WIP: OTA-1580: Further tests for oc adm upgrade status'

[petr-muller]

TBD (also needs polishing)

[openshift-ci-robot]

@petr-muller: This pull request references OTA-1580 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 task to target the "4.20.0" version, but no target version was set.

Details

In response to this:

TBD (also needs polishing)

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]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: petr-muller

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:

• pkg/monitortests/cli/adm_upgrade/OWNERS [petr-muller]

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

[petr-muller]

Will be superseded by #30109 but I am interested in the CI job results here. Will close after that.

[openshift-ci]

@petr-muller: 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-ovn-upgrade	ee0d11d	link	true	/test e2e-gcp-ovn-upgrade
ci/prow/e2e-aws-ovn-upgrade	ee0d11d	link	false	/test e2e-aws-ovn-upgrade
ci/prow/e2e-aws-ovn-single-node-upgrade	ee0d11d	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-ovn-single-node-serial	ee0d11d	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-metal-ipi-ovn-dualstack	ee0d11d	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-aws-disruptive	ee0d11d	link	false	/test e2e-aws-disruptive
ci/prow/okd-scos-e2e-aws-ovn	ee0d11d	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-gcp-ovn-techpreview-serial-1of2	ee0d11d	link	false	/test e2e-gcp-ovn-techpreview-serial-1of2
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2	ee0d11d	link	false	/test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-metal-ipi-ovn	ee0d11d	link	false	/test e2e-metal-ipi-ovn
ci/prow/e2e-gcp-ovn-rt-upgrade	ee0d11d	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-vsphere-ovn	ee0d11d	link	true	/test e2e-vsphere-ovn

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

Job Failure Risk Analysis for sha: ee0d11d

Job Name	Failure Risk
pull-ci-openshift-origin-main-e2e-aws-disruptive	Medium [sig-node] static pods should start after being created Potential external regression detected for High Risk Test analysis --- [bz-Etcd] clusteroperator/etcd should not change condition/Available Potential external regression detected for High Risk Test analysis

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: ee0d11d

• "[sig-cli][OCPFeatureGate:UpgradeStatus] oc adm upgrade status control plane section is consistent" [Total: 34, Pass: 34, Fail: 0, Flake: 0]
• "[sig-cli][OCPFeatureGate:UpgradeStatus] oc adm upgrade status health section is consistent" [Total: 34, Pass: 34, Fail: 0, Flake: 0]
• "[sig-cli][OCPFeatureGate:UpgradeStatus] oc adm upgrade status never fails" [Total: 34, Pass: 34, Fail: 0, Flake: 0]
• "[sig-cli][OCPFeatureGate:UpgradeStatus] oc adm upgrade status output has expected layout" [Total: 34, Pass: 34, Fail: 0, Flake: 0]
• "[sig-cli][OCPFeatureGate:UpgradeStatus] oc adm upgrade status workers section is consistent" [Total: 34, Pass: 34, Fail: 0, Flake: 0]

[petr-muller]

/close

[openshift-ci]

@petr-muller: Closed this PR.

Details

In response to this:

/close

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.