Use docker driver for minikube installation test.

[benluddy]

Something changed (either in a new minikube version or the runner bump
to Ubuntu 20) and minikube isn't honoring the vm-driver=none
config. I'm guessing that it has something to do with running minikube start
with sudo but minikube config without. This test now uses the
newer docker driver in an effort to sidestep the issue completely.

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: benluddy

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 [benluddy]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[benluddy]

This only touches Github Actions config. Overriding the pricier downstream tests.

/override e2e-aws-console-olm
/override e2e-aws-olm
/override e2e-gcp
/override e2e-upgrade

[openshift-ci-robot]

@benluddy: /override requires a failed status context to operate on.
The following unknown contexts were given:

• e2e-aws-console-olm
• e2e-aws-olm
• e2e-gcp
• e2e-upgrade

Only the following contexts were expected:

• ci/prow/e2e-aws-console-olm
• ci/prow/e2e-aws-olm
• ci/prow/e2e-gcp
• ci/prow/e2e-upgrade
• ci/prow/images
• ci/prow/unit
• ci/prow/verify
• tide

In response to this:

This only touches Github Actions config. Overriding the pricier downstream tests.

/override e2e-aws-console-olm
/override e2e-aws-olm
/override e2e-gcp
/override e2e-upgrade

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.

[benluddy]

@benluddy: /override requires a failed status context to operate on.
The following unknown contexts were given:

* `e2e-aws-console-olm`

* `e2e-aws-olm`

* `e2e-gcp`

* `e2e-upgrade`

Only the following contexts were expected:

* `ci/prow/e2e-aws-console-olm`

* `ci/prow/e2e-aws-olm`

* `ci/prow/e2e-gcp`

* `ci/prow/e2e-upgrade`

* `ci/prow/images`

* `ci/prow/unit`

* `ci/prow/verify`

* `tide`

/override ci/prow/e2e-aws-console-olm
/override ci/prow/e2e-aws-olm
/override ci/prow/e2e-gcp
/override ci/prow/e2e-upgrade

[openshift-ci-robot]

@benluddy: Overrode contexts on behalf of benluddy: ci/prow/e2e-aws-console-olm, ci/prow/e2e-aws-olm, ci/prow/e2e-gcp, ci/prow/e2e-upgrade

In response to this:

@benluddy: /override requires a failed status context to operate on.
The following unknown contexts were given:

* `e2e-aws-console-olm`

* `e2e-aws-olm`

* `e2e-gcp`

* `e2e-upgrade`

Only the following contexts were expected:

* `ci/prow/e2e-aws-console-olm`

* `ci/prow/e2e-aws-olm`

* `ci/prow/e2e-gcp`

* `ci/prow/e2e-upgrade`

* `ci/prow/images`

* `ci/prow/unit`

* `ci/prow/verify`

* `tide`

/override ci/prow/e2e-aws-console-olm
/override ci/prow/e2e-aws-olm
/override ci/prow/e2e-gcp
/override ci/prow/e2e-upgrade

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.

[exdx]

/lgtm

[openshift-ci]

@benluddy: The following test failed, say /retest to rerun all failed tests:

Test name	Commit	Details	Rerun command
ci/prow/e2e-gcp	daa7fd2	link	/test e2e-gcp

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

[benluddy]

/cherry-pick release-4.6

Downstream jobs on release-4.6 are upset about the failure of this job.

[openshift-cherrypick-robot]

@benluddy: new pull request created: #1988

In response to this:

/cherry-pick release-4.6

Downstream jobs on release-4.6 are upset about the failure of this job.

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.