Bug 2064408: use ubi instead of busybox for untar image

[jmrodri]

Description of the change: Switch to using UBI instead of busybox for the untar image.

Motivation for the change: With the docker rate limiting in place, busybox is not a great choice for the untar image. Therefore, switching to UBI to avoid that limit.

[openshift-ci[bot]]

@jmrodri: This pull request references Bugzilla bug 2064408, which is invalid:

• expected Bugzilla bug 2064408 to depend on a bug targeting a release in 4.10.0, 4.10.z and in one of the following states: VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE), but no dependents were found

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

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/222): >Bug 2064408: use ubi instead of busybox for untar image Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[jmrodri]

/bugzilla refresh

[openshift-ci[bot]]

@jmrodri: This pull request references Bugzilla bug 2064408, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug

* bug is open, matching expected state (open) * bug target release (4.9.z) matches configured target release for branch (4.9.z) * bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST) * dependent bug [Bugzilla bug 2064413](https://bugzilla.redhat.com/show_bug.cgi?id=2064413) is in the state CLOSED (CURRENTRELEASE), which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA), CLOSED (CURRENTRELEASE)) * dependent [Bugzilla bug 2064413](https://bugzilla.redhat.com/show_bug.cgi?id=2064413) targets the "4.10.0" release, which is one of the valid target releases: 4.10.0, 4.10.z * bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (jfan@redhat.com), skipping review request.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/222#issuecomment-1068352250): >/bugzilla refresh Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[openshift-bot]

/retest-required

Please review the full test history for this PR and help us cut down flakes.

[jmrodri]

/test e2e-aws-ansible

[jmrodri]

/test e2e-aws-helm

[jmrodri]

/test e2e-aws-ansible

[jmrodri]

/test e2e-aws-helm

[jmrodri]

/test e2e-aws-helm

[jmrodri]

/test e2e-aws-ansible

[jmrodri]

/label backport-risk-assessed

[jmrodri]

/test e2e-aws-ansible

[jmrodri]

/test e2e-aws-helm

[openshift-ci[bot]]

@jmrodri: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).

[michaelryanpeter]

/label docs-approved

[emmajiafan]

/label cherry-pick-approved

[openshift-ci[bot]]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: asmacdo, jmrodri

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: - ~~[OWNERS](https://github.com/openshift/ocp-release-operator-sdk/blob/release-4.9/OWNERS)~~ [asmacdo,jmrodri] Approvers can indicate their approval by writing `/approve` in a comment Approvers can cancel approval by writing `/approve cancel` in a comment

[openshift-ci[bot]]

@jmrodri: All pull requests linked via external trackers have merged:

• openshift/ocp-release-operator-sdk#222

Bugzilla bug 2064408 has been moved to the MODIFIED state.

In response to [this](https://github.com/openshift/ocp-release-operator-sdk/pull/222): >Bug 2064408: use ubi instead of busybox for untar image Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.