Skip to content

OCPBUGS-77023: Fast track shouldn't happen when firmware update is in progress#376

Open
hroyrh wants to merge 1 commit intoopenshift:release-4.21from
hroyrh:ocpbugs-59807
Open

OCPBUGS-77023: Fast track shouldn't happen when firmware update is in progress#376
hroyrh wants to merge 1 commit intoopenshift:release-4.21from
hroyrh:ocpbugs-59807

Conversation

@hroyrh
Copy link

@hroyrh hroyrh commented Feb 16, 2026

Assisted-By: Claude
Change-Id: I91118a4b19b4a26145ee2a5a12287f874fee246b

(cherry picked from commit dd7e863)

Assisted-By: Claude
Change-Id: I91118a4b19b4a26145ee2a5a12287f874fee246b
Signed-off-by: Himanshu Roy <hroy@redhat.com>
(cherry picked from commit dd7e863)
@openshift-ci
Copy link

openshift-ci bot commented Feb 16, 2026

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hroyrh
Once this PR has been reviewed and has the lgtm label, please assign zaneb for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

@hroyrh hroyrh changed the title Fast track shouldn't happen when firmware update is in progress OCPBUGS-59807: Fast track shouldn't happen when firmware update is in progress Feb 17, 2026
@openshift-ci-robot openshift-ci-robot added jira/severity-critical Referenced Jira bug's severity is critical 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 17, 2026
@openshift-ci-robot
Copy link

@hroyrh: This pull request references Jira Issue OCPBUGS-59807, which is invalid:

  • expected the bug to target the "4.21.z" version, but no target version was set
  • expected Jira Issue OCPBUGS-59807 to depend on a bug targeting a version in 4.22.0 and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but no dependents were found

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:

Assisted-By: Claude
Change-Id: I91118a4b19b4a26145ee2a5a12287f874fee246b

(cherry picked from commit dd7e863)

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.

@hroyrh
Copy link
Author

hroyrh commented Feb 17, 2026

/retest-required

@openshift-ci
Copy link

openshift-ci bot commented Feb 17, 2026

@hroyrh: 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/unit 8c12893 link true /test unit

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.

@hroyrh hroyrh changed the title OCPBUGS-59807: Fast track shouldn't happen when firmware update is in progress Fast track shouldn't happen when firmware update is in progress Feb 18, 2026
@hroyrh hroyrh changed the title Fast track shouldn't happen when firmware update is in progress OCPBUGS-77023: Fast track shouldn't happen when firmware update is in progress Feb 18, 2026
@hroyrh
Copy link
Author

hroyrh commented Feb 18, 2026

/jira refresh

1 similar comment
@hroyrh
Copy link
Author

hroyrh commented Feb 18, 2026

/jira refresh

@openshift-ci-robot
Copy link

@hroyrh: This pull request references Jira Issue OCPBUGS-77023, which is invalid:

  • expected dependent Jira Issue OCPBUGS-59807 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA), but it is ASSIGNED 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:

/jira refresh

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/severity-critical Referenced Jira bug's severity is critical 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

Development

Successfully merging this pull request may close these issues.

2 participants

Comments