fix hypershift workflow to set qe-app-registry on hosted cluster

[kuiwang02]

/cc @Xia-Zhao-rh

during checking failing case in https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/logs/periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive/1870535735631679488/artifacts/aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive/openshift-extended-test-disruptive/build-log.txt, we find the case which use operator from qe-app-registry catsrc fails

after checking, we find the workflow cucushift-installer-rehearse-aws-ipi-ovn-hypershift-public-private-guest does not install qe-app-registry on hosted cluster. it uses chain cucushift-installer-rehearse-aws-ipi-ovn-hypershift-public-private-provision, and after hypershift-aws-create, no step to create it on hosted cluster.

we find similar workflow cucushift-installer-rehearse-aws-ipi-ovn-hypershift-private-guest, it uses chain cucushift-installer-rehearse-aws-ipi-ovn-hypershift-private-provision, and after hypershift-aws-create, it uses cucushift-hypershift-extended-enable-qe-catalogsource to create it on hosted cluster.

So, here I add cucushift-hypershift-extended-enable-qe-catalogsource into chain cucushift-installer-rehearse-aws-ipi-ovn-hypershift-public-private-provision to see if it resolve the issue.

[kuiwang02]

/pj-rehearse ack periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive

[openshift-ci-robot]

@kuiwang02: now processing your pj-rehearse request. Please allow up to 10 minutes for jobs to trigger or cancel.

[openshift-ci-robot]

@kuiwang02: job(s): ack either don't exist or were not found to be affected, and cannot be rehearsed

[kuiwang02]

per https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/pr-logs/pull/openshift_release/60179/rehearse-60179-periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive/1872194548646547456/artifacts/aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive/cucushift-hypershift-extended-enable-qe-catalogsource/build-log.txt, the qa-app-registry is created on hosted cluster successfully.

per https://gcsweb-qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/gcs/qe-private-deck/pr-logs/pull/openshift_release/60179/rehearse-60179-periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive/1872194548646547456/artifacts/aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive/openshift-extended-test-disruptive/build-log.txt, the case which take qe-app-registry pass.

for https://qe-private-deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/qe-private-deck/pr-logs/pull/openshift_release/60179/rehearse-60179-periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive/1872194548646547456, the failing has nothing with this change because it is failing in other steps.

so, the change works.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: kuiwang02
Once this PR has been reviewed and has the lgtm label, please assign liangquanli930 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:

• ci-operator/step-registry/cucushift/installer/rehearse/aws/ipi/ovn/hypershift/public-private/provision/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]

[REHEARSALNOTIFIER]
@kuiwang02: the pj-rehearse plugin accommodates running rehearsal tests for the changes in this PR. Expand 'Interacting with pj-rehearse' for usage details. The following rehearsable tests have been affected by this change:

Test name	Repo	Type	Reason
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-public-private-guest-f28	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive	N/A	periodic	Registry content changed
periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-public-private-mgmt-f28	N/A	periodic	Registry content changed

Interacting with pj-rehearse

Comment: /pj-rehearse to run up to 5 rehearsals
Comment: /pj-rehearse skip to opt-out of rehearsals
Comment: /pj-rehearse {test-name}, with each test separated by a space, to run one or more specific rehearsals
Comment: /pj-rehearse more to run up to 10 rehearsals
Comment: /pj-rehearse max to run up to 25 rehearsals
Comment: /pj-rehearse auto-ack to run up to 5 rehearsals, and add the rehearsals-ack label on success
Comment: /pj-rehearse abort to abort all active rehearsals
Comment: /pj-rehearse network-access-allowed to allow rehearsals of tests that have the restrict_network_access field set to false. This must be executed by an openshift org member who is not the PR author

Once you are satisfied with the results of the rehearsals, comment: /pj-rehearse ack to unblock merge. When the rehearsals-ack label is present on your PR, merge will no longer be blocked by rehearsals.
If you would like the rehearsals-ack label removed, comment: /pj-rehearse reject to re-block merging.

[openshift-ci]

@kuiwang02: The following test 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/rehearse/periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive	57ed415	link	unknown	/pj-rehearse periodic-ci-openshift-openshift-tests-private-release-4.14-amd64-nightly-aws-ipi-ovn-hypershift-pub-private-guest-f28-destructive

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.

[kuiwang02]

@LiangquanLi930 could you please review and approve it if it is ok? thanks

I already tested it and the result is #60179 (comment). per the result, it passes.

@heliubj18 I find you also are working on it with PR #60181, and actually it is same issue, so suggest to merge PR #60179

Thanks

[kuiwang02]

/cc @LiangquanLi930 @heliubj18