MCO-1595: MCO-1596: MCO-1597: MCO-1598: Add 4/5 MachineConfigNode e2e tests

[isabella-janssen]

Notes

• All tests should run successfully with a cluster built on 4.19.0-0.nightly-2025-03-21-030708 or later with tech preview enabled.
• The tests for MCO-1597 & MCO-1598 are both tagged Slow, as they often take longer than 5 minutes to run. To have these tests run automatically, we will need to create a suite at a later time (Slack ref), but the tests can still be run locally.

MCO-1595: Validate MCN properties

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1596: Validate MCN condition status transitions

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1597: Validate MCN condition status on node degrade

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial][Slow]Should properly report MCN conditions on node degrade [apigroup:machineconfiguration.openshift.io]"

MCO-1598: Validate MCN on node creation and deletion

Note that this test is skipped for Single Node Openshift

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial][Slow]Should properly create and remove MCN on node creation and deletion [apigroup:machineconfiguration.openshift.io]"

[openshift-ci-robot]

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

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]

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]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: isabella-janssen
Once this PR has been reviewed and has the lgtm label, please assign dgoodwin for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• OWNERS

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

[openshift-ci-robot]

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

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 MCO-1595 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.19.0" version, but no target version was set.

In response to this:

MCO-1595: Validate MCN properties

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

MCO-1595: Validate MCN properties

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

MCO-1595: Validate MCN properties

To run, launch a cluster using openshift/machine-config-operator#4876. (Clusterbot: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview)

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

MCO-1595: Validate MCN properties

To run, launch a cluster using openshift/machine-config-operator#4876: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview) and use the following command.

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

To run the tests, launch a cluster using MCO PR 4876.
Clusterbot: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview

MCO-1595: Validate MCN properties

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

To run the tests, launch a cluster using MCO PR 4876.
Clusterbot example command: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview

MCO-1595: Validate MCN properties

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

To run the tests, launch a cluster using MCO PR 4876.
Clusterbot example command: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview

MCO-1595: Validate MCN properties

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

MCO-1595: Validate MCN properties

To run the test, launch a cluster using MCO PR 4876.
Clusterbot example command: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1596: Validate MCN condition status transitions

This test can be run using any 4.19 cluster with tech preview enabled.

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

MCO-1595: Validate MCN properties

To run the test, launch a cluster using MCO PR 4876.
Clusterbot example command: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1596: Validate MCN condition status transitions

This test can be run using any 4.19 cluster with tech preview enabled.

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

MCO-1595: Validate MCN properties

To run the test, launch a cluster using MCO PR 4876.
Clusterbot example command: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1596: Validate MCN condition status transitions

This test can be run using any 4.19 cluster with tech preview enabled.

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1597: Validate MCN condition status on node degrade

This test can be run using any 4.19 cluster with tech preview enabled.

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should properly report MCN conditions on node degrade [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-ci-robot]

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

In response to this:

MCO-1595: Validate MCN properties

To run the test, launch a cluster using MCO PR 4876.
Clusterbot example command: launch 4.19,openshift/machine-config-operator#4876 aws,techpreview

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1596: Validate MCN condition status transitions

This test can be run using any 4.19 cluster with tech preview enabled.

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1597: Validate MCN condition status on node degrade

This test can be run using any 4.19 cluster with tech preview enabled.

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should properly report MCN conditions on node degrade [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]"

MCO-1598: Validate MCN on node creation and deletion

./openshift-tests run-test "[sig-mco][OCPFeatureGate:MachineConfigNode][Serial] Should properly create and remove MCN on node creation and deletion [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/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.

[openshift-trt]

Job Failure Risk Analysis for sha: afd3335

Job Name	Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	MissingData
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-bgp-techpreview	IncompleteTests Tests for this run (104) are below the historical average (2455): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-okd-e2e-gcp	IncompleteTests Tests for this run (15) are below the historical average (79): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-trt]

Job Failure Risk Analysis for sha: afd3335

Job Name	Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	IncompleteTests Tests for this run (93) are below the historical average (248): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-dualstack-bgp-techpreview	IncompleteTests Tests for this run (104) are below the historical average (2455): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-okd-e2e-gcp	IncompleteTests Tests for this run (15) are below the historical average (79): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[isabella-janssen]

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

[openshift-trt]

Job Failure Risk Analysis for sha: da4e47b

Job Name	Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	MissingData
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling	Medium [sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times Potential external regression detected for High Risk Test analysis --- [bz-etcd][invariant] alert/etcdMembersDown should not be at or above info Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-gcp-disruptive	Medium [bz-Etcd] clusteroperator/etcd should not change condition/Available Potential external regression detected for High Risk Test analysis --- [sig-node] static pods should start after being created Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-okd-e2e-gcp	IncompleteTests Tests for this run (17) are below the historical average (78): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

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

New Test Risks for sha: da4e47b

Job Name	New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-techpreview-serial	High - "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]" is a new test that failed 1 time(s) against the current commit

New tests seen in this PR at sha: da4e47b

• "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]" [Total: 2, Pass: 2, Fail: 0, Flake: 0]
• "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]" [Total: 2, Pass: 1, Fail: 1, Flake: 0]

[openshift-trt]

Job Failure Risk Analysis for sha: 9519f3c

Job Name	Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	MissingData
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling	Medium [sig-architecture] platform pods in ns/openshift-multus should not exit an excessive amount of times Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling	Low [bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded This test has passed 0.00% of 1 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-disruptive	Medium [bz-Etcd] clusteroperator/etcd should not change condition/Available Potential external regression detected for High Risk Test analysis --- [sig-node] static pods should start after being created Potential external regression detected for High Risk Test analysis --- [sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator Potential external regression detected for High Risk Test analysis --- [sig-node] node-lifecycle detects unexpected not ready node Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling	High [sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times This test has passed 99.94% of 6438 runs on release 4.19 [Overall] in the last week. --- [bz-etcd][invariant] alert/etcdMembersDown should not be at or above info This test has passed 99.88% of 6434 runs on release 4.19 [Overall] in the last week.

[openshift-trt]

Job Failure Risk Analysis for sha: 9519f3c

Job Name	Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	MissingData
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling	Medium [sig-architecture] platform pods in ns/openshift-multus should not exit an excessive amount of times Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling	Low [bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded This test has passed 0.00% of 1 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-disruptive	Medium [bz-Etcd] clusteroperator/etcd should not change condition/Available Potential external regression detected for High Risk Test analysis --- [sig-node] static pods should start after being created Potential external regression detected for High Risk Test analysis --- [sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator Potential external regression detected for High Risk Test analysis --- [sig-node] node-lifecycle detects unexpected not ready node Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling	High [sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times This test has passed 99.94% of 6438 runs on release 4.19 [Overall] in the last week. --- [bz-etcd][invariant] alert/etcdMembersDown should not be at or above info This test has passed 99.88% of 6434 runs on release 4.19 [Overall] in the last week.

[isabella-janssen]

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

[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-aws-ovn-etcd-scaling	9519f3c	link	false	/test e2e-aws-ovn-etcd-scaling
ci/prow/e2e-aws-disruptive	9519f3c	link	false	/test e2e-aws-disruptive
ci/prow/e2e-openstack-ovn	9519f3c	link	false	/test e2e-openstack-ovn
ci/prow/e2e-metal-ipi-ovn	9519f3c	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-gcp-disruptive	9519f3c	link	false	/test e2e-gcp-disruptive
ci/prow/e2e-gcp-ovn-etcd-scaling	9519f3c	link	false	/test e2e-gcp-ovn-etcd-scaling
ci/prow/e2e-vsphere-ovn-etcd-scaling	9519f3c	link	false	/test e2e-vsphere-ovn-etcd-scaling
ci/prow/okd-e2e-gcp	9519f3c	link	false	/test okd-e2e-gcp
ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview	9519f3c	link	false	/test e2e-metal-ipi-ovn-dualstack-bgp-techpreview
ci/prow/e2e-aws-csi	9519f3c	link	false	/test e2e-aws-csi
ci/prow/e2e-aws	9519f3c	link	false	/test e2e-aws
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6	9519f3c	link	false	/test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-openstack-serial	9519f3c	link	false	/test e2e-openstack-serial
ci/prow/e2e-azure-ovn-etcd-scaling	9519f3c	link	false	/test e2e-azure-ovn-etcd-scaling
ci/prow/e2e-aws-ovn-single-node-serial	9519f3c	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	9519f3c	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-metal-ipi-serial-ovn-ipv6	9519f3c	link	false	/test e2e-metal-ipi-serial-ovn-ipv6
ci/prow/e2e-azure-ovn-upgrade	9519f3c	link	false	/test e2e-azure-ovn-upgrade
ci/prow/e2e-gcp-fips-serial	9519f3c	link	false	/test e2e-gcp-fips-serial
ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	9519f3c	link	false	/test 4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback
ci/prow/e2e-aws-ovn-single-node-techpreview-serial	9519f3c	link	false	/test e2e-aws-ovn-single-node-techpreview-serial
ci/prow/e2e-gcp-ovn-techpreview-serial	9519f3c	link	false	/test e2e-gcp-ovn-techpreview-serial

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

Job Failure Risk Analysis for sha: 9519f3c

Job Name	Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	IncompleteTests Tests for this run (85) are below the historical average (237): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)
pull-ci-openshift-origin-main-e2e-aws-ovn-etcd-scaling	Medium [sig-architecture] platform pods in ns/openshift-multus should not exit an excessive amount of times Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-techpreview-serial	High
pull-ci-openshift-origin-main-e2e-azure-ovn-etcd-scaling	Low [bz-Cloud Compute] clusteroperator/control-plane-machine-set should not change condition/Degraded This test has passed 0.00% of 1 runs on release 4.19 [Architecture:amd64 FeatureSet:default Installer:ipi JobTier:rare Network:ovn NetworkStack:ipv4 Owner:eng Platform:azure SecurityMode:default Topology:ha Upgrade:none] in the last week.
pull-ci-openshift-origin-main-e2e-gcp-disruptive	Medium [bz-Etcd] clusteroperator/etcd should not change condition/Available Potential external regression detected for High Risk Test analysis --- [sig-node] static pods should start after being created Potential external regression detected for High Risk Test analysis --- [sig-arch] events should not repeat pathologically for ns/openshift-kube-apiserver-operator Potential external regression detected for High Risk Test analysis --- [sig-node] node-lifecycle detects unexpected not ready node Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling	High [sig-architecture] platform pods in ns/openshift-etcd should not exit an excessive amount of times This test has passed 99.94% of 6380 runs on release 4.19 [Overall] in the last week. --- [bz-etcd][invariant] alert/etcdMembersDown should not be at or above info This test has passed 99.87% of 6376 runs on release 4.19 [Overall] in the last week.

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

New Test Risks for sha: 9519f3c

Job Name	New Test Risk
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-techpreview-serial	High - "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]" is a new test, was only seen in one job, and failed 1 time(s) against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-techpreview-serial	High - "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]" is a new test, was only seen in one job, and failed 1 time(s) against the current commit.
pull-ci-openshift-origin-main-e2e-aws-ovn-single-node-techpreview-serial	Medium - "[sig-trt] Skipped annotations present" is a new test, and was only seen in one job.

New tests seen in this PR at sha: 9519f3c

• "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should have MCN properties matching associated node properties [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]" [Total: 1, Pass: 0, Fail: 1, Flake: 0]
• "[sig-mco][OCPFeatureGate:MachineConfigNodes] [Serial]Should properly transition through MCN conditions on node update [apigroup:machineconfiguration.openshift.io] [Suite:openshift/conformance/serial]" [Total: 1, Pass: 0, Fail: 1, Flake: 0]
• "[sig-trt] Skipped annotations present" [Total: 1, Pass: 1, Fail: 0, Flake: 1]

[djoshy]

/payload-job ?

[openshift-ci]

@djoshy: it appears that you have attempted to use some version of the payload command, but your comment was incorrectly formatted and cannot be acted upon. See the docs for usage info.

[djoshy]

/payload-job help

[openshift-ci]

@djoshy: trigger 0 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

[djoshy]

/payload-job periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-techpreview-serial periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview-serial

[openshift-ci]

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

• periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial
• periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/c95e2290-0ff1-11f0-97bd-ba68be73eb1a-0

[isabella-janssen]

/payload-job periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-techpreview-serial periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview-serial

[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-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.19-e2e-azure-ovn-techpreview-serial
• periodic-ci-openshift-release-master-ci-4.19-e2e-gcp-ovn-techpreview-serial
• periodic-ci-openshift-release-master-nightly-4.19-e2e-vsphere-ovn-techpreview-serial

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/ff848910-101c-11f0-9c6c-ccb796a017c3-0

[openshift-trt]

Job Failure Risk Analysis for sha: 62e3d28

Job Name	Failure Risk
pull-ci-openshift-origin-main-4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback	MissingData
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling	Medium [sig-architecture] platform pods in ns/openshift-multus should not exit an excessive amount of times Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-kube-apiserver-rollout	IncompleteTests Tests for this run (103) are below the historical average (1319): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)

[openshift-trt]

Job Failure Risk Analysis for sha: 62e3d28

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-gcp-ovn-etcd-scaling	Medium [sig-architecture] platform pods in ns/openshift-multus should not exit an excessive amount of times Potential external regression detected for High Risk Test analysis
pull-ci-openshift-origin-main-e2e-metal-ipi-ovn-kube-apiserver-rollout	IncompleteTests Tests for this run (103) are below the historical average (1319): IncompleteTests (not enough tests ran to make a reasonable risk analysis; this could be due to infra, installation, or upgrade problems)