OCPBUGS-74237: Update MCN tests to better handle condition transitions through the "Unknown" state

[isabella-janssen]

This updates the MCO's Should properly transition through MCN conditions on rebootless node update MCN test to better handle cases where a test progresses so quickly that the "Unknown" state for a condition is missed.

[openshift-ci-robot]

Pipeline controller notification
This repo is configured to use the pipeline controller. Second-stage tests will be triggered either automatically or after lgtm label is added, depending on the repository configuration. The pipeline controller will automatically detect which contexts are required and will utilize /test Prow commands to trigger the second stage.

For optional jobs, comment /test ? to see a list of all defined jobs. To trigger manually all jobs from second stage use /pipeline required command.

This repository is configured in: automatic mode

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci]

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

• periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-serial-1of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ed4ef340-f656-11f0-9d8c-addd25b6ef13-0

[openshift-ci-robot]

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

Requesting review from QA contact:
/cc @sergiordlr

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

Details

In response to this:

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-74237, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.22.0) matches configured target version for branch (4.22.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, POST)

Requesting review from QA contact:
/cc @sergiordlr

Details

In response to this:

This updates the MCO's Should properly transition through MCN conditions on rebootless node update MCN test to better handle cases where a test progresses so quickly that the "Unknown" state for a condition is missed.

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]

Scheduling required tests:
/test e2e-aws-csi
/test e2e-aws-ovn-fips
/test e2e-aws-ovn-microshift
/test e2e-aws-ovn-microshift-serial
/test e2e-aws-ovn-serial-1of2
/test e2e-aws-ovn-serial-2of2
/test e2e-gcp-csi
/test e2e-gcp-ovn
/test e2e-gcp-ovn-upgrade
/test e2e-metal-ipi-ovn-ipv6
/test e2e-vsphere-ovn
/test e2e-vsphere-ovn-upi

[openshift-trt]

Risk analysis has seen new tests most likely introduced by this PR.
Please ensure that new tests meet guidelines for naming and stability.

New tests seen in this PR at sha: ec042d0

• "[Monitor:crd-version-checker][Jira:"kube-apiserver"] monitor test crd-version-checker cleanup" [Total: 11, Pass: 11, Fail: 0, Flake: 0]
• "[Monitor:crd-version-checker][Jira:"kube-apiserver"] monitor test crd-version-checker collection" [Total: 11, Pass: 11, Fail: 0, Flake: 0]
• "[Monitor:crd-version-checker][Jira:"kube-apiserver"] monitor test crd-version-checker interval construction" [Total: 11, Pass: 11, Fail: 0, Flake: 0]
• "[Monitor:crd-version-checker][Jira:"kube-apiserver"] monitor test crd-version-checker preparation" [Total: 11, Pass: 11, Fail: 0, Flake: 0]
• "[Monitor:crd-version-checker][Jira:"kube-apiserver"] monitor test crd-version-checker setup" [Total: 11, Pass: 11, Fail: 0, Flake: 0]
• "[Monitor:crd-version-checker][Jira:"kube-apiserver"] monitor test crd-version-checker test evaluation" [Total: 11, Pass: 11, Fail: 0, Flake: 0]
• "[Monitor:crd-version-checker][Jira:"kube-apiserver"] monitor test crd-version-checker writing to storage" [Total: 11, Pass: 11, Fail: 0, Flake: 0]
• "[Monitor:crd-version-checker][sig-api-machinery] CRDs with new API versions should not change storage version immediately" [Total: 11, Pass: 11, Fail: 0, Flake: 0]

[isabella-janssen]

/retest-required

[djoshy]

/lgtm

Seems sane to me, thanks for the fix-up! I guess we'll be double checking True state in some cases, but I suppose that's fine, let's see how the e2e behaves

[openshift-ci]

@djoshy: This PR was included in a payload test run from openshift/machine-config-operator#5582
trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-nightly-4.22-e2e-aws-ovn-serial-1of2

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ced38df0-f7a9-11f0-9d0e-2d5d72054b41-0

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

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

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

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• test/extended/machine_config/OWNERS [djoshy,isabella-janssen]

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

[isabella-janssen]

/verified by payload rehearsal

See payload rehearsal of test change here: openshift/machine-config-operator#5582 (comment)

[openshift-ci-robot]

@isabella-janssen: This PR has been marked as verified by payload rehearsal.

Details

In response to this:

/verified by payload rehearsal

See payload rehearsal of test change here: openshift/machine-config-operator#5582 (comment)

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: all tests passed!

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.

[openshift-ci-robot]

@isabella-janssen: Jira Issue Verification Checks: Jira Issue OCPBUGS-74237
✔️ 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-74237 has been moved to the MODIFIED state and will move to the VERIFIED state when the change is available in an accepted nightly payload. 🕓

Details

In response to this:

This updates the MCO's Should properly transition through MCN conditions on rebootless node update MCN test to better handle cases where a test progresses so quickly that the "Unknown" state for a condition is missed.

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-merge-robot]

Fix included in accepted release 4.22.0-0.nightly-2026-01-24-213011

[isabella-janssen]

/cherrypick release-4.21

[openshift-cherrypick-robot]

@isabella-janssen: new pull request created: #30729

Details

In response to this:

/cherrypick release-4.21

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.