OCPBUGS-66225: bump deployment ProgressDeadlineSeconds to 120s

[tjungblu]

This bumps the deadline seconds of the operand deployment, in many failures we're just scratching the timeout and cause a degraded blip.

Also required for openshift/origin#30755

[openshift-ci-robot]

@tjungblu: This pull request references Jira Issue OCPBUGS-66225, which is valid. The bug has been moved to the POST state.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xiuwang

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

Details

In response to this:

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-robot]

@tjungblu: This pull request references Jira Issue OCPBUGS-66225, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @xiuwang

Details

In response to this:

This bumps the deadline seconds of the operand deployment, in many failures we're just scratching the timeout and cause a degraded blip.

Also required for openshift/origin#30755

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.

[tjungblu]

@ricardomaraschini do you mind to take a quick look once you have some time? this is a rather quick fix 🤣

[xiuwang]

/verified by @xiuwang

I did not observe image registry Degraded during upgrade 4.21.0-0.nightly-2026-02-25-232937 to 4.22.0-0-2026-03-02-080619-test-ci-ln-pdchwib-latest(included this pr).
and

oc get deployment -n openshift-image-registry image-registry -o yaml | grep progressDeadlineSeconds
  progressDeadlineSeconds: 120

[openshift-ci-robot]

@xiuwang: This PR has been marked as verified by @xiuwang.

Details

In response to this:

/verified by @xiuwang

I did not observe image registry Degraded during upgrade 4.21.0-0.nightly-2026-02-25-232937 to 4.22.0-0-2026-03-02-080619-test-ci-ln-pdchwib-latest(included this pr).
and

oc get deployment -n openshift-image-registry image-registry -o yaml | grep progressDeadlineSeconds
 progressDeadlineSeconds: 120

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.

[xiuwang]

/test hypershift-e2e-aks

[ricardomaraschini]

/approve

[flavianmissi]

This bumps the deadline seconds of the operand deployment, in many failures we're just scratching the timeout and cause a degraded blip.

I'm curious - is this a new check for us, or did things slow down over time?

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flavianmissi, ricardomaraschini, tjungblu

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:

• OWNERS [flavianmissi,ricardomaraschini]

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

[tjungblu]

/retest

[tjungblu]

/retest

[openshift-ci]

@tjungblu: The following tests 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/images	18e33e7	link	true	/test images
ci/prow/e2e-aws-ovn-upgrade	18e33e7	link	true	/test e2e-aws-ovn-upgrade
ci/prow/e2e-hypershift	18e33e7	link	true	/test e2e-hypershift
ci/prow/e2e-aws-ovn-image-registry	18e33e7	link	true	/test e2e-aws-ovn-image-registry
ci/prow/e2e-aws-ovn	18e33e7	link	true	/test e2e-aws-ovn
ci/prow/e2e-aws-operator	18e33e7	link	true	/test e2e-aws-operator
ci/prow/e2e-hypershift-conformance	18e33e7	link	true	/test e2e-hypershift-conformance

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.