MCO-1370: Add boot image configmap test to openshift/origin

[djoshy]

This adds one more boot image update test to the MCO's test suite. This test ensures that the boot image configmap "stamp" action by the operator is always done, as long as at least one master node is up to date.

[openshift-ci-robot]

@djoshy: This pull request references MCO-1304 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to [this](https://github.com/openshift/origin/pull/29219): >This adds one more boot image update related test to the MCO's test suite. This test ensures that the boot image configmap "stamp" action by the operator is always done, as long as at least one master node is up to date. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

@djoshy: This pull request references MCO-1304 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to [this](https://github.com/openshift/origin/pull/29219): >This adds one more boot image update test to the MCO's test suite. This test ensures that the boot image configmap "stamp" action by the operator is always done, as long as at least one master node is up to date. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[openshift-ci-robot]

@djoshy: This pull request references MCO-1370 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.18.0" version, but no target version was set.

In response to [this](https://github.com/openshift/origin/pull/29219): >This adds one more boot image update test to the MCO's test suite. This test ensures that the boot image configmap "stamp" action by the operator is always done, as long as at least one master node is up to date. Instructions for interacting with me using PR comments are available [here](https://prow.ci.openshift.org/command-help?repo=openshift%2Forigin). If you have questions or suggestions related to my behavior, please file an issue against the [openshift-eng/jira-lifecycle-plugin](https://github.com/openshift-eng/jira-lifecycle-plugin/issues/new) repository.

[djoshy]

/test e2e-aws-ovn-single-node-techpreview-serial /test e2e-gcp-fips-serial

[openshift-trt-bot]

Job Failure Risk Analysis for sha: 537023931214e5f296c1f8fea6642aca7ff15e3d

Job Name	Failure Risk
pull-ci-openshift-origin-master-e2e-aws-ovn-single-node-upgrade	High [sig-network] pods should successfully create sandboxes by writing network status This test has passed 98.31% of 237 runs on release 4.18 [Architecture:amd64 FeatureSet:default Installer:ipi Network:ovn NetworkStack:ipv4 Platform:aws SecurityMode:default Topology:single Upgrade:micro] in the last week.

[djoshy]

/test e2e-aws-ovn-single-node-techpreview-serial /test e2e-gcp-fips-serial

[yuqi-zhang]

/approve

[xueqzhan]

/lgtm

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: djoshy, xueqzhan, yuqi-zhang

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](https://github.com/openshift/origin/blob/master/OWNERS)~~ [xueqzhan] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[openshift-ci[bot]]

@djoshy: 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-aws-ovn-single-node	537023931214e5f296c1f8fea6642aca7ff15e3d	link	false	/test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-single-node-upgrade	537023931214e5f296c1f8fea6642aca7ff15e3d	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-techpreview-serial	537023931214e5f296c1f8fea6642aca7ff15e3d	link	false	/test e2e-aws-ovn-single-node-techpreview-serial
ci/prow/e2e-agnostic-ovn-cmd	537023931214e5f296c1f8fea6642aca7ff15e3d	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-gcp-fips-serial	537023931214e5f296c1f8fea6642aca7ff15e3d	link	false	/test e2e-gcp-fips-serial

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes-sigs/prow](https://github.com/kubernetes-sigs/prow/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 35b2af79cb20654cf5142d7ccaeca4f2050dcea6 and 2 for PR HEAD 537023931214e5f296c1f8fea6642aca7ff15e3d in total

[openshift-bot]

[ART PR BUILD NOTIFIER]

Distgit: openshift-enterprise-tests This PR has been included in build openshift-enterprise-tests-container-v4.18.0-202410250313.p0.ga01d147.assembly.stream.el9. All builds following this will include this PR.