Skip to content

[release-4.18] OCPBUGS-76598: Increase agent-installer pre-network-manager timeout#10299

Open
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-10284-to-release-4.18
Open

[release-4.18] OCPBUGS-76598: Increase agent-installer pre-network-manager timeout#10299
openshift-cherrypick-robot wants to merge 1 commit intoopenshift:release-4.18from
openshift-cherrypick-robot:cherry-pick-10284-to-release-4.18

Conversation

@openshift-cherrypick-robot
Copy link

@openshift-cherrypick-robot openshift-cherrypick-robot commented Feb 11, 2026

This is an automated cherry-pick of #10284

/assign bfournie

@bfournie
OCPBUGS-63386: Increase agent-installer pre-network-manager timeout
1f2219f 
We have a report that a baremetal installation with VLAN interfaces
can require longer than the current setting for the timeout of
the pre-network-manager-config service. Increasing it to 300
seconds.
@openshift-cherrypick-robot openshift-cherrypick-robot mentioned this pull request Feb 11, 2026
Merged
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 11, 2026

@openshift-cherrypick-robot: Jira Issue OCPBUGS-74940 has been cloned as Jira Issue OCPBUGS-76598. Will retitle bug to link to clone.
/retitle [release-4.18] OCPBUGS-76598: Increase agent-installer pre-network-manager timeout

Details

In response to this:

This is an automated cherry-pick of #10284

/assign bfournie

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot changed the title [release-4.18] OCPBUGS-74940: Increase agent-installer pre-network-manager timeout [release-4.18] OCPBUGS-76598: Increase agent-installer pre-network-manager timeout Feb 11, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. labels Feb 11, 2026
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Feb 11, 2026

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-76598, which is invalid:

  • expected dependent Jira Issue OCPBUGS-74940 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ON_QA instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

Details

In response to this:

This is an automated cherry-pick of #10284

/assign bfournie

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 11, 2026

@openshift-cherrypick-robot: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-agent-compact-ipv4-appliance-diskimage 1f2219f link false /test e2e-agent-compact-ipv4-appliance-diskimage

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@bfournie
Copy link
Contributor

bfournie commented Feb 13, 2026

/label backport-risk-assessed
/approve

@openshift-ci openshift-ci bot added the backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. label Feb 13, 2026
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Feb 13, 2026

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: bfournie

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Feb 13, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@bfournie bfournie Awaiting requested review from bfournie

@pawanpinjarkar pawanpinjarkar Awaiting requested review from pawanpinjarkar

Assignees

@bfournie bfournie

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. backport-risk-assessed Indicates a PR to a release branch has been evaluated and considered safe to accept. jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-moderate Referenced Jira bug's severity is moderate for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@openshift-cherrypick-robot @openshift-ci-robot @bfournie