[release-4.19] OCPBUGS-60767: Update the OnClusterBuild payload tests to reflect the validation rule requiring MCP & MOSC names to match

[isabella-janssen]

Closes: OCPBUGS-60767

- What I did
This is a manual cherrypick of #5249 since the automated cherrypick failed. This backport is required since we are backporting the API validation rule requiring MCP & MOSC names to match (see openshift/api#2449).

- How to verify it
The OnClusterBuild tests in the MCO disruptive test suite triggered against the API backport PR introducing the new validation rule should not fail with the following error, MachineOSConfig name must match the referenced MachineConfigPool name; can only have one MachineOSConfig per MachineConfigPool.

See payload test: https://pr-payload-tests.ci.openshift.org/runs/ci/9788cd30-7e94-11f0-8c45-45136dc11bb6-0

- Description for the changelog
OCPBUGS-60559: Update the OnClusterBuild tests to reflect validation rule requiring the MOSC and MCP names to match

[isabella-janssen]

/jira cherry-pick OCPBUGS-60559

[openshift-ci-robot]

@isabella-janssen: Jira Issue OCPBUGS-60559 has been cloned as Jira Issue OCPBUGS-60767. Will retitle bug to link to clone.
/retitle OCPBUGS-60767: Update the OnClusterBuild payload tests to reflect the validation rule requiring MCP & MOSC names to match

In response to this:

/jira cherry-pick OCPBUGS-60559

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]

@isabella-janssen: This pull request references Jira Issue OCPBUGS-60767, which is invalid:

• expected dependent Jira Issue OCPBUGS-60559 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.

In response to this:

…g names

- What I did

- How to verify it

- Description for the changelog

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.

[isabella-janssen]

/payload-job periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-vsphere-mco-disruptive periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-aws-mco-disruptive periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-azure-mco-disruptive periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-gcp-mco-disruptive

[openshift-ci]

@isabella-janssen: trigger 4 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-vsphere-mco-disruptive
• periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-aws-mco-disruptive
• periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-azure-mco-disruptive
• periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-gcp-mco-disruptive

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ce04f8d0-7e93-11f0-91dc-c4b9351690a8-0

[openshift-ci]

@isabella-janssen: This PR was included in a payload test run from openshift/api#2449
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-machine-config-operator-release-4.19-periodics-e2e-aws-mco-disruptive

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/9788cd30-7e94-11f0-8c45-45136dc11bb6-0

[umohnani8]

Thanks @isabella-jansse! LGTM

[isabella-janssen]

/jira refresh

[openshift-ci-robot]

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

7 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.19.z) matches configured target version for branch (4.19.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-60559 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-60559 targets the "4.20.0" version, which is one of the valid target versions: 4.20.0
• bug has dependents

Requesting review from QA contact:
/cc @sergiordlr

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

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.

[RishabhSaini]

/lgtm

[pablintino]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: isabella-janssen, pablintino, RishabhSaini

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 [RishabhSaini,isabella-janssen,pablintino]

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

[isabella-janssen]

/label backport-risk-assessed

The scope of this change is limited to the OnClusterBuild regression tests & rehearsal payloads tests have been run.

[isabella-janssen]

/test unit

[openshift-ci]

@isabella-janssen: all tests passed!

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.

[openshift-ci-robot]

@isabella-janssen: Jira Issue OCPBUGS-60767: All pull requests linked via external trackers have merged:

• openshift/machine-config-operator#5258

Jira Issue OCPBUGS-60767 has been moved to the MODIFIED state.

In response to this:

Closes: OCPBUGS-60767

- What I did
This is a manual cherrypick of #5249 since the automated cherrypick failed. This backport is required since we are backporting the API validation rule requiring MCP & MOSC names to match (see openshift/api#2449).

- How to verify it
The OnClusterBuild tests in the MCO disruptive test suite triggered against the API backport PR introducing the new validation rule should not fail with the following error, MachineOSConfig name must match the referenced MachineConfigPool name; can only have one MachineOSConfig per MachineConfigPool.

See payload test: https://pr-payload-tests.ci.openshift.org/runs/ci/9788cd30-7e94-11f0-8c45-45136dc11bb6-0

- Description for the changelog
OCPBUGS-60559: Update the OnClusterBuild tests to reflect validation rule requiring the MOSC and MCP names to match

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

[ART PR BUILD NOTIFIER]

Distgit: ose-machine-config-operator
This PR has been included in build ose-machine-config-operator-container-v4.19.0-202508281608.p0.gf56b790.assembly.stream.el9.
All builds following this will include this PR.