Skip to content

Conversation

@isabella-janssen
Copy link
Member

@isabella-janssen isabella-janssen commented Nov 19, 2025

With the implementation of MCO-1870 being introduced in openshift/machine-config-operator#5411, the MachineConfigNode conditions will be different when a cluster has the ImageModeStatusReporting FeatureGate enabled. The condition transitions for this situation are tested in the ImageModeStatusReporting tests, so this test can simply be skipped without losing test coverage.

To verify this change, confirm that the Should properly transition through MCN conditions on rebootless node update test is skipped in tech preview test clusters (periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial) and not skipped in default clusters (periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial).

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Nov 19, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 19, 2025

@isabella-janssen: This pull request references MCO-1870 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.21.0" version, but no target version was set.

In response to this:

With the implementation of MCO-1870 being introduced in openshift/machine-config-operator#5411, the MachineConfigNode conditions will be different when a cluster is TechPreview and has the ImageModeStatusReporting FeatureGate enabled. The condition transitions for this situation are tested in the ImageModeStatusReporting tests, so this test can simply be skipped without losing test coverage.

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.

1 similar comment
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 19, 2025

@isabella-janssen: This pull request references MCO-1870 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.21.0" version, but no target version was set.

In response to this:

With the implementation of MCO-1870 being introduced in openshift/machine-config-operator#5411, the MachineConfigNode conditions will be different when a cluster is TechPreview and has the ImageModeStatusReporting FeatureGate enabled. The condition transitions for this situation are tested in the ImageModeStatusReporting tests, so this test can simply be skipped without losing test coverage.

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
Copy link

Pipeline controller notification
This repository 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. Review these jobs and use /test <job> to manually trigger optional jobs most likely to be impacted by the proposed changes.

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Nov 19, 2025
@openshift-ci-robot
Copy link

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-vsphere-ovn
/test e2e-vsphere-ovn-upi
/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-vsphere-ovn
/test e2e-vsphere-ovn-upi
/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-vsphere-ovn
/test e2e-vsphere-ovn-upi

@isabella-janssen isabella-janssen changed the title MCO-1870: Skip MCN condition transition test in TechPreview clusters MCO-1870: Skip MCN condition transition test in clusters with ImageModeStatusReporting FeatureGate is enabled Nov 20, 2025
@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 20, 2025

@isabella-janssen: This pull request references MCO-1870 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.21.0" version, but no target version was set.

In response to this:

With the implementation of MCO-1870 being introduced in openshift/machine-config-operator#5411, the MachineConfigNode conditions will be different when a cluster has the ImageModeStatusReporting FeatureGate enabled. The condition transitions for this situation are tested in the ImageModeStatusReporting tests, so this test can simply be skipped without losing test coverage.

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
Copy link
Member Author

/payload-job periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-1of2 periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-2of2 periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

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

  • periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-1of2
  • periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-2of2
  • periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/bd5d3a20-c5c8-11f0-998f-21e1b9a8c3be-0

@jmguzik
Copy link

jmguzik commented Nov 20, 2025

This repository is using now pipeline controller to divide tests and have 2 stage pipeline. To know more how to trigger tests in second stage, in case they are not triggered for whatever reason, please see: https://docs.ci.openshift.org/docs/how-tos/creating-a-pipeline/

@isabella-janssen
Copy link
Member Author

Thank you for sharing @jmguzik!

@isabella-janssen
Copy link
Member Author

/payload-job periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-1of2 periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-2of2 periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

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

  • periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-1of2
  • periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive-techpreview-2of2
  • periodic-ci-openshift-machine-config-operator-release-4.21-periodics-e2e-aws-mco-disruptive

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/8185d880-c619-11f0-8b54-d8bde81dad9c-0

@isabella-janssen
Copy link
Member Author

/payload-job periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-1of2 periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-2of2 periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-1of3 periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-2of3 periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-3of3

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

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

  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-1of2
  • periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial-2of2
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-1of3
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-2of3
  • periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial-3of3

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1e82d830-c620-11f0-8342-029b0f6e63e6-0

@openshift-ci-robot
Copy link

openshift-ci-robot commented Nov 20, 2025

@isabella-janssen: This pull request references MCO-1870 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.21.0" version, but no target version was set.

In response to this:

With the implementation of MCO-1870 being introduced in openshift/machine-config-operator#5411, the MachineConfigNode conditions will be different when a cluster has the ImageModeStatusReporting FeatureGate enabled. The condition transitions for this situation are tested in the ImageModeStatusReporting tests, so this test can simply be skipped without losing test coverage.

To verify this change, confirm that the Should properly transition through MCN conditions on rebootless node update test is skipped in tech preview test clusters and not skipped in default clusters.

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
Copy link

openshift-ci-robot commented Nov 20, 2025

@isabella-janssen: This pull request references MCO-1870 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.21.0" version, but no target version was set.

In response to this:

With the implementation of MCO-1870 being introduced in openshift/machine-config-operator#5411, the MachineConfigNode conditions will be different when a cluster has the ImageModeStatusReporting FeatureGate enabled. The condition transitions for this situation are tested in the ImageModeStatusReporting tests, so this test can simply be skipped without losing test coverage.

To verify this change, confirm that the Should properly transition through MCN conditions on rebootless node update test is skipped in tech preview test clusters (periodic-ci-openshift-release-master-ci-4.21-e2e-aws-ovn-techpreview-serial) and not skipped in default clusters (periodic-ci-openshift-release-master-nightly-4.21-e2e-aws-ovn-serial).

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.

@djoshy
Copy link
Contributor

djoshy commented Nov 20, 2025

/lgtm

seems sane to me, feel free to unhold when ready

/hold

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 20, 2025
@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Nov 20, 2025
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 20, 2025

[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

Needs approval from an approver in each of these files:

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

@isabella-janssen
Copy link
Member Author

/verified by @isabella-janssen

Verified by running payload rehearsals:

✅ The MCN test ran in a default cluster (where ImageModeStatusReporting is not enabled) - https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30505-nightly-4.21-e2e-aws-ovn-serial-1of2/1991519387365937152
✅ The MCN test was skipped in a tech preview cluster (where ImageModeStatusReporting is enabled) - https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30505-ci-4.21-e2e-aws-ovn-techpreview-serial-2of3/1991519389022687232

@openshift-ci-robot openshift-ci-robot added the verified Signifies that the PR passed pre-merge verification criteria label Nov 20, 2025
@openshift-ci-robot
Copy link

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

In response to this:

/verified by @isabella-janssen

Verified by running payload rehearsals:

✅ The MCN test ran in a default cluster (where ImageModeStatusReporting is not enabled) - https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30505-nightly-4.21-e2e-aws-ovn-serial-1of2/1991519387365937152
✅ The MCN test was skipped in a tech preview cluster (where ImageModeStatusReporting is enabled) - https://prow.ci.openshift.org/view/gs/test-platform-results/logs/openshift-origin-30505-ci-4.21-e2e-aws-ovn-techpreview-serial-2of3/1991519389022687232

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
Copy link
Member Author

/unhold

The payload rehearsals ran as expected, so this should be good to go.

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 20, 2025
@isabella-janssen
Copy link
Member Author

/pipeline required

@openshift-ci-robot
Copy link

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-vsphere-ovn
/test e2e-vsphere-ovn-upi
/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-vsphere-ovn
/test e2e-vsphere-ovn-upi
/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-vsphere-ovn
/test e2e-vsphere-ovn-upi

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 96ce99d and 2 for PR HEAD cda83de in total

@isabella-janssen
Copy link
Member Author

/retest-required

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD fc6ec0c and 1 for PR HEAD cda83de in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 353bc51 and 0 for PR HEAD cda83de in total

@openshift-ci-robot
Copy link

/hold

Revision cda83de was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 21, 2025
@isabella-janssen
Copy link
Member Author

/unhold

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Nov 21, 2025
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 353bc51 and 2 for PR HEAD cda83de in total

@openshift-trt
Copy link

openshift-trt bot commented Nov 21, 2025

Job Failure Risk Analysis for sha: cda83de

Job Name Failure Risk
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-ipv6 IncompleteTests
Tests for this run (12) are below the historical average (2109): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

@isabella-janssen
Copy link
Member Author

/test e2e-metal-ipi-ovn-ipv6

@isabella-janssen
Copy link
Member Author

/retest-required

@openshift-ci
Copy link
Contributor

openshift-ci bot commented Nov 21, 2025

@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-merge-bot openshift-merge-bot bot merged commit eb52c92 into openshift:main Nov 21, 2025
20 checks passed
@isabella-janssen isabella-janssen deleted the mco-1870 branch November 24, 2025 12:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged. verified Signifies that the PR passed pre-merge verification criteria

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants