OTA-1581: Skip UpgradeStatus test on HyperShift

[petr-muller]

The oc adm upgrade status has no support for HyperShift where update procedure is different especially around nodes:

• assumes MCP existence
• no NodePool knowledge
• no knowledge of separate management / hosted cluster

[openshift-ci-robot]

@petr-muller: This pull request references OTA-1581 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.

In response to this:

The oc adm upgrade status has no support for HyperShift where update
procedure is different especially around nodes:

• assumes MCP existence
• no NodePool knowledge
• no knowledge of separate management / hosted cluster

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]

@petr-muller: This pull request references OTA-1581 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.

In response to this:

The oc adm upgrade status has no support for HyperShift where update procedure is different especially around nodes:

• assumes MCP existence
• no NodePool knowledge
• no knowledge of separate management / hosted cluster

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]

/uncc @DavidHurta
/cc @hongkailiu

[hongkailiu]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hongkailiu, 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:

• test/extended/cli/adm_upgrade/OWNERS [hongkailiu,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-robot]

/retest-required

Remaining retests: 0 against base HEAD c5c90f8 and 2 for PR HEAD 49e9a67 in total

[openshift-ci-robot]

/retest-required

Remaining retests: 0 against base HEAD 2e1dac3 and 1 for PR HEAD 49e9a67 in total

[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-techpreview	49e9a67	link	false	/test e2e-gcp-ovn-techpreview
ci/prow/e2e-aws-ovn-single-node-upgrade	49e9a67	link	false	/test e2e-aws-ovn-single-node-upgrade
ci/prow/e2e-aws-proxy	49e9a67	link	false	/test e2e-aws-proxy
ci/prow/e2e-aws-ovn-edge-zones	49e9a67	link	false	/test e2e-aws-ovn-edge-zones
ci/prow/e2e-aws-disruptive	49e9a67	link	false	/test e2e-aws-disruptive
ci/prow/e2e-metal-ipi-ovn	49e9a67	link	false	/test e2e-metal-ipi-ovn
ci/prow/okd-scos-e2e-aws-ovn	49e9a67	link	false	/test okd-scos-e2e-aws-ovn
ci/prow/e2e-aws-ovn-cgroupsv2	49e9a67	link	false	/test e2e-aws-ovn-cgroupsv2
ci/prow/e2e-openstack-ovn	49e9a67	link	false	/test e2e-openstack-ovn
ci/prow/e2e-gcp-ovn-techpreview-serial-2of2	49e9a67	link	false	/test e2e-gcp-ovn-techpreview-serial-2of2

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.