OCPBUGS-61114: Fix ImageBuildDegraded Status updates

[umohnani8]

Closes https://issues.redhat.com/browse/OCPBUGS-61114

- What I did
After an image was built and rolled out successfully, and we triggered a new build, the ImageBuildDegraded status wasn't updating correctly as it kept focusing on the successful build and not the build currently active. Fix the logic to be able to keep track of the active build instead and update the status accordingly.

- How to verify it

1. Create an MOSC that succeeds
2. After the build is successful and rolled out, edit the MOSC
3. Ensure the ImageBuildDegraded status option is following the active build and updating correctly

- Description for the changelog
ImageBuildDegraded status option should correctly update by following the status of the active build.

[openshift-ci-robot]

@umohnani8: This pull request references Jira Issue OCPBUGS-61114, which is invalid:

• expected the bug to target the "4.21.0" version, but no target version was set

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.

In response to this:

Closes https://issues.redhat.com/browse/OCPBUGS-61114

- What I did
After an image was built and rolled out successfully, and we triggered a new build, the ImageBuildDegraded status wasn't updating correctly as it kept focusing on the successful build and not the build currently active. Fix the logic to be able to keep track of the active build instead and update the status accordingly.

- How to verify it

1. Create an MOSC that succeeds
2. After the build is successful and rolled out, edit the MOSC
3. Ensure the ImageBuildDegraded status option is following the active build and updating correctly

- Description for the changelog
ImageBuildDegraded status option should correctly update by following the status of the active build.

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: umohnani8

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [umohnani8]

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

[umohnani8]

/jira refresh

[openshift-ci-robot]

@umohnani8: This pull request references Jira Issue OCPBUGS-61114, 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.21.0) matches configured target version for branch (4.21.0)
• bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

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.

[openshift-ci]

@umohnani8: 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/e2e-gcp-op-single-node	ae88523	link	true	/test e2e-gcp-op-single-node
ci/prow/e2e-gcp-op-1of2	ae88523	link	true	/test e2e-gcp-op-1of2
ci/prow/e2e-aws-mco-disruptive	ae88523	link	false	/test e2e-aws-mco-disruptive
ci/prow/e2e-gcp-mco-disruptive	ae88523	link	false	/test e2e-gcp-mco-disruptive
ci/prow/e2e-aws-ovn-windows	ae88523	link	false	/test e2e-aws-ovn-windows
ci/prow/e2e-azure-ovn-upgrade-out-of-change	ae88523	link	false	/test e2e-azure-ovn-upgrade-out-of-change
ci/prow/e2e-gcp-op-ocl	ae88523	link	false	/test e2e-gcp-op-ocl
ci/prow/e2e-hypershift	ae88523	link	true	/test e2e-hypershift
ci/prow/bootstrap-unit	ae88523	link	false	/test bootstrap-unit
ci/prow/verify	ae88523	link	true	/test verify
ci/prow/e2e-agent-compact-ipv4	ae88523	link	false	/test e2e-agent-compact-ipv4
ci/prow/unit	ae88523	link	true	/test unit

Full PR test history. Your PR dashboard.

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.