NO-JIRA: oc adm upgrade status: Skip test in multihop update jobs

[petr-muller]

Checks in updateLifecycle only make sense in jobs that update at most once, so skip the tests when multiple hops were made.

Example failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-from-stable-4.18-e2e-aws-ovn-upgrade/1958216717935054848

[openshift-ci-robot]

@petr-muller: This pull request explicitly references no jira issue.

In response to this:

Checks in updateLifecycle only make sense in jobs that update at most
once, so skip the tests when multiple hops were made.

Example failure: https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-from-stable-4.18-e2e-aws-ovn-upgrade/1958216717935054848

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.

[petr-muller]

/payload-job periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-from-stable-4.18-e2e-aws-ovn-upgrade

[openshift-ci]

@petr-muller: trigger 1 job(s) for the /payload-(with-prs|job|aggregate|job-with-prs|aggregate-with-prs) command

• periodic-ci-openshift-release-master-ci-4.20-upgrade-from-stable-4.19-from-stable-4.18-e2e-aws-ovn-upgrade

See details on https://pr-payload-tests.ci.openshift.org/runs/ci/1269eac0-7e9a-11f0-9fc4-c8f2de660622-0

[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

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

[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-aws-ovn-single-node-serial	dfc8218	link	false	/test e2e-aws-ovn-single-node-serial
ci/prow/e2e-gcp-ovn-techpreview	dfc8218	link	false	/test e2e-gcp-ovn-techpreview
ci/prow/e2e-metal-ipi-ovn-dualstack	dfc8218	link	false	/test e2e-metal-ipi-ovn-dualstack
ci/prow/e2e-gcp-ovn-rt-upgrade	dfc8218	link	false	/test e2e-gcp-ovn-rt-upgrade
ci/prow/e2e-aws-ovn-fips	dfc8218	link	true	/test e2e-aws-ovn-fips
ci/prow/e2e-metal-ipi-ovn-ipv6	dfc8218	link	true	/test e2e-metal-ipi-ovn-ipv6
ci/prow/e2e-metal-ipi-virtualmedia	dfc8218	link	false	/test e2e-metal-ipi-virtualmedia
ci/prow/e2e-aws-ovn	dfc8218	link	false	/test e2e-aws-ovn
ci/prow/e2e-aws-ovn-kube-apiserver-rollout	dfc8218	link	false	/test e2e-aws-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-techpreview-serial-1of2	dfc8218	link	false	/test e2e-gcp-ovn-techpreview-serial-1of2
ci/prow/e2e-agnostic-ovn-cmd	dfc8218	link	false	/test e2e-agnostic-ovn-cmd
ci/prow/e2e-metal-ipi-ovn-kube-apiserver-rollout	dfc8218	link	false	/test e2e-metal-ipi-ovn-kube-apiserver-rollout
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2	dfc8218	link	false	/test e2e-gcp-ovn-techpreview-serial-2of2
ci/prow/e2e-aws-ovn-single-node-upgrade	dfc8218	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/okd-scos-e2e-aws-ovn	dfc8218	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-metal-ipi-ovn-dualstack-local-gateway	dfc8218	link	false	/test e2e-metal-ipi-ovn-dualstack-local-gateway
ci/prow/e2e-openstack-ovn	dfc8218	link	false	/test e2e-openstack-ovn
ci/prow/e2e-gcp-ovn	dfc8218	link	true	/test e2e-gcp-ovn
ci/prow/e2e-aws-ovn-serial-1of2	dfc8218	link	true	/test e2e-aws-ovn-serial-1of2
ci/prow/e2e-aws-disruptive	dfc8218	link	false	/test e2e-aws-disruptive
ci/prow/e2e-gcp-csi	dfc8218	link	false	/test e2e-gcp-csi
ci/prow/e2e-gcp-ovn-upgrade	dfc8218	link	true	/test e2e-gcp-ovn-upgrade

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.