TRT-2082: Revert "MCO-1520: Add MachineConfigNode e2e tests"#29682
Conversation
openshift-ci-robot
added
the
jira/valid-reference
|
@xueqzhan: This pull request references TRT-2082 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 bug to target the "4.19.0" version, but no target version was set. DetailsIn 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
Bot
added
the
approved
|
@xueqzhan: This pull request references TRT-2082 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 bug to target the "4.19.0" version, but no target version was set. DetailsIn 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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: stbenjam, xueqzhan The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/skip |
|
@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-gcp-csi, ci/prow/e2e-gcp-disruptive, ci/prow/e2e-gcp-fips-serial, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-etcd-scaling, ci/prow/e2e-gcp-ovn-rt-upgrade, ci/prow/e2e-gcp-ovn-upgrade, ci/prow/e2e-hypershift-conformance, ci/prow/e2e-metal-ipi-ovn, ci/prow/e2e-metal-ipi-ovn-dualstack, ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview, ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway, ci/prow/e2e-metal-ipi-ovn-ipv6, ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout, ci/prow/e2e-metal-ipi-serial, ci/prow/e2e-metal-ipi-serial-ovn-ipv6, ci/prow/e2e-metal-ipi-virtualmedia, ci/prow/e2e-openstack-ovn, ci/prow/e2e-openstack-serial, ci/prow/okd-e2e-gcp, ci/prow/okd-scos-e2e-aws-ovn DetailsIn 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 kubernetes-sigs/prow repository. |
|
/skip |
|
/override ci/prow/e2e-aws-ovn-edge-zones |
|
@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/e2e-aws-ovn-edge-zones, ci/prow/e2e-aws-ovn-fips, ci/prow/e2e-aws-ovn-microshift, ci/prow/e2e-aws-ovn-microshift-serial, ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-vsphere-ovn, ci/prow/e2e-vsphere-ovn-upi DetailsIn 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 kubernetes-sigs/prow repository. |
|
/override ci/prow/e2e-metal-ipi-ovn-dualstack |
|
@stbenjam: /override requires failed status contexts, check run or a prowjob name to operate on.
Only the following failed contexts/checkruns were expected:
If you are trying to override a checkrun that has a space in it, you must put a double quote on the context. DetailsIn 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 kubernetes-sigs/prow repository. |
|
/override ci/prow/e2e-metal-ipi-ovn-dualstack |
|
@stbenjam: Overrode contexts on behalf of stbenjam: ci/prow/4.12-upgrade-from-stable-4.11-e2e-aws-ovn-upgrade-rollback, ci/prow/e2e-agnostic-ovn-cmd, ci/prow/e2e-aws, ci/prow/e2e-aws-csi, ci/prow/e2e-aws-disruptive, ci/prow/e2e-aws-ovn, ci/prow/e2e-aws-ovn-cgroupsv2, ci/prow/e2e-aws-ovn-edge-zones, ci/prow/e2e-aws-ovn-etcd-scaling, ci/prow/e2e-aws-ovn-fips, ci/prow/e2e-aws-ovn-kube-apiserver-rollout, ci/prow/e2e-aws-ovn-microshift, ci/prow/e2e-aws-ovn-microshift-serial, ci/prow/e2e-aws-ovn-serial, ci/prow/e2e-aws-ovn-single-node, ci/prow/e2e-aws-ovn-single-node-serial, ci/prow/e2e-aws-ovn-single-node-upgrade, ci/prow/e2e-aws-ovn-upgrade, ci/prow/e2e-aws-proxy, ci/prow/e2e-azure, ci/prow/e2e-azure-ovn-etcd-scaling, ci/prow/e2e-azure-ovn-upgrade, ci/prow/e2e-gcp-csi, ci/prow/e2e-gcp-disruptive, ci/prow/e2e-gcp-fips-serial, ci/prow/e2e-gcp-ovn, ci/prow/e2e-gcp-ovn-etcd-scaling, ci/prow/e2e-gcp-ovn-rt-upgrade, ci/prow/e2e-gcp-ovn-upgrade, ci/prow/e2e-hypershift-conformance, ci/prow/e2e-metal-ipi-ovn, ci/prow/e2e-metal-ipi-ovn-dualstack, ci/prow/e2e-metal-ipi-ovn-dualstack-bgp-techpreview, ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway, ci/prow/e2e-metal-ipi-ovn-ipv6, ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout, ci/prow/e2e-metal-ipi-serial, ci/prow/e2e-metal-ipi-serial-ovn-ipv6, ci/prow/e2e-metal-ipi-virtualmedia, ci/prow/e2e-openstack-ovn, ci/prow/e2e-openstack-serial, ci/prow/e2e-vsphere-ovn, ci/prow/e2e-vsphere-ovn-dualstack-primaryv6, ci/prow/e2e-vsphere-ovn-etcd-scaling DetailsIn 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 kubernetes-sigs/prow repository. |
|
@xueqzhan: all tests passed! Full PR test history. Your PR dashboard. DetailsInstructions 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. |
|
[ART PR BUILD NOTIFIER] Distgit: openshift-enterprise-tests |
4 participants
Reverts #29596; tracked by TRT-2082
Per OpenShift policy, we are reverting this breaking change to get CI and/or nightly payloads flowing again.
Since this PR landed, we observed an extra sets of node state change. This might have caused extra sets of pods exits.
Here is an example failure job: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-[…]ci-4.19-e2e-aws-ovn-techpreview-serial/1911166459887751168
Compare with an old working one: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-[…]ci-4.19-e2e-aws-ovn-techpreview-serial/1910984894356393984
In the spyglass chart you will see the extra set of nodestate change.
Slack thread: https://redhat-internal.slack.com/archives/C01CQA76KMX/p1744631682980549
To unrevert this, revert this PR, and layer an additional separate commit on top that addresses the problem. Before merging the unrevert, please run these jobs on the PR and check the result of to confirm the fix has corrected the problem:
/payload-aggregate periodic-ci-openshift-release-master-ci-4.19-e2e-aws-ovn-techpreview-serial 5
Since this is not a perma failing test, the above command will run the job 5 times.
CC: @isabella-janssen