[release-4.9] OCPBUGS-1010: Download yq in upi installer containers

[openshift-cherrypick-robot]

This is an automated cherry-pick of #6285

/assign sdodson

[openshift-ci-robot]

@openshift-cherrypick-robot: Detected clone of Jira Issue OCPBUGS-784 with correct target version. Retitling PR to link to clone:
/retitle [release-4.9] OCPBUGS-1010: Download yq in upi installer containers

Details

In response to this:

This is an automated cherry-pick of #6285

/assign sdodson

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/test-infra repository.

[openshift-ci-robot]

@openshift-cherrypick-robot: This pull request references Jira Issue OCPBUGS-1010, which is invalid:

• expected Jira Issue OCPBUGS-1010 to depend on a bug targeting a version in 4.10.0, 4.10.z and in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), but no dependents were found

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

Details

In response to this:

This is an automated cherry-pick of #6285

/assign sdodson

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/test-infra repository.

[openshift-ci]

@openshift-cherrypick-robot: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

Details

In response to this:

[release-4.9] OCPBUGS-1010: Download yq in upi installer containers

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/test-infra repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

Approval requirements bypassed by manually added approval.

This pull-request has been approved by:

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:

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

/retest-required

Remaining retests: 0 against base HEAD 8b46510 and 2 for PR HEAD f339a0a in total

[openshift-ci-robot]

@openshift-cherrypick-robot: All pull requests linked via external trackers have merged:

Jira Issue OCPBUGS-1010 has been moved to the MODIFIED state.

Details

In response to this:

This is an automated cherry-pick of #6285

/assign sdodson

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/test-infra repository.

[openshift-ci]

@openshift-cherrypick-robot: 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-crc	f339a0a	link	false	/test e2e-crc
ci/prow/e2e-aws-workers-rhel8	f339a0a	link	false	/test e2e-aws-workers-rhel8
ci/prow/e2e-libvirt	f339a0a	link	false	/test e2e-libvirt

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/test-infra repository. I understand the commands that are listed here.

[jianlinliu]

@sdodson thanks for your quick update and approve.

[jianlinliu]

/cherry-pick release-4.8

[openshift-cherrypick-robot]

@jianlinliu: new pull request created: #6322

Details

In response to this:

/cherry-pick release-4.8

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/test-infra repository.

[sdodson]

@jianlinliu how far back did you want to backport this?

[sdodson]

@jianlinliu how far back did you want to backport this?

nevermind i see now you picked it to 4.8 too

[jianlinliu]

how far back did you want to backport this?

This depends on our test plan, especially upgrade testing, some upgrade testing is trying to install a very old version of source cluster, if I saw some similar issues of missing yq-go, I will continue backport it to that version accordingly.