[release-4.19] OCPBUGS-61284: Make MCN e2e tests blocking

[isabella-janssen]

Note: This is a manual cherrypick of #4972.

- What I did
Moved MCN e2e tests from non-blocking e2e-techpreview suite to blocking e2e suite.

- How to verify it

• MCN e2e tests should pass in the e2e-gcp-op test suite
• MCN e2e tests should no longer run in the e2e-gcp-op-techpreview test suite

- Description for the changelog
Make MCN e2e tests part of the blocking e2e-gcp-op presubmit job.

[isabella-janssen]

/jira cherrypick OCPBUGS-61283

[openshift-ci-robot]

@isabella-janssen: Jira Issue OCPBUGS-61283 has been cloned as Jira Issue OCPBUGS-61284. Will retitle bug to link to clone.
/retitle OCPBUGS-61284: Make MCN e2e tests blocking

In response to this:

/jira cherrypick OCPBUGS-61283

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-61284, which is invalid:

• release note text must be set and not match the template OR release note type must be set to "Release Note Not Required". For more information you can reference the OpenShift Bug Process.
• expected dependent Jira Issue OCPBUGS-61283 to target a version in 4.20.0, but it targets "4.19.z" 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:

Note: This is a manual cherrypick of #4972.

- What I did
Moved MCN e2e tests from non-blocking e2e-techpreview suite to blocking e2e suite.

- How to verify it
Run e2e tests with /test e2e-gcp-op.

- Description for the changelog
Make MCN e2e tests part of the blocking e2e-gcp-op presubmit job.

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]

/jira refresh

[openshift-ci-robot]

@isabella-janssen: This pull request references Jira Issue OCPBUGS-61284, 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-61283 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-61283 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.

[openshift-ci-robot]

@isabella-janssen: This pull request references Jira Issue OCPBUGS-61284, which is valid.

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 POST, which is one of the valid states (NEW, ASSIGNED, POST)
• release note type set to "Release Note Not Required"
• dependent bug Jira Issue OCPBUGS-61283 is in the state Closed (Done), which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), CLOSED (DONE-ERRATA))
• dependent Jira Issue OCPBUGS-61283 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

In response to this:

Note: This is a manual cherrypick of #4972.

- What I did
Moved MCN e2e tests from non-blocking e2e-techpreview suite to blocking e2e suite.

- How to verify it

• MCN e2e tests should pass in the e2e-gcp-op test suite
• MCN e2e tests should no longer run in the e2e-gcp-op-techpreview test suite

- Description for the changelog
Make MCN e2e tests part of the blocking e2e-gcp-op presubmit job.

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]

/retest-required

[umohnani8]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: isabella-janssen, 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 [isabella-janssen,umohnani8]

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 e2e-gcp-op passed and the scope of this change is limited.

[isabella-janssen]

/verified by running the e2e-gcp-op test and checking the MCN test statuses

[openshift-ci-robot]

@isabella-janssen: This PR has been marked as verified by running the e2e-gcp-op test and checking the MCN test statuses.

In response to this:

/verified by running the e2e-gcp-op test and checking the MCN test statuses

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]

/retest-required

[openshift-ci]

@isabella-janssen: 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-mco-disruptive	c4c77b6	link	false	/test e2e-gcp-mco-disruptive
ci/prow/e2e-aws-mco-disruptive	c4c77b6	link	false	/test e2e-aws-mco-disruptive
ci/prow/e2e-azure-ovn-upgrade-out-of-change	c4c77b6	link	false	/test e2e-azure-ovn-upgrade-out-of-change

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]

/retest-required

Remaining retests: 0 against base HEAD 1a3a559 and 2 for PR HEAD c4c77b6 in total

[openshift-ci-robot]

@isabella-janssen: Jira Issue Verification Checks: Jira Issue OCPBUGS-61284
✔️ This pull request was pre-merge verified.
✔️ All associated pull requests have merged.
✔️ All associated, merged pull requests were pre-merge verified.

Jira Issue OCPBUGS-61284 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

In response to this:

Note: This is a manual cherrypick of #4972.

- What I did
Moved MCN e2e tests from non-blocking e2e-techpreview suite to blocking e2e suite.

- How to verify it

• MCN e2e tests should pass in the e2e-gcp-op test suite
• MCN e2e tests should no longer run in the e2e-gcp-op-techpreview test suite

- Description for the changelog
Make MCN e2e tests part of the blocking e2e-gcp-op presubmit job.

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-202509110437.p0.g37499ce.assembly.stream.el9.
All builds following this will include this PR.

[openshift-merge-robot]

Fix included in accepted release 4.19.0-0.nightly-2025-09-11-104048