Set the USER env for e2e jobs

[flaper87]

Sadly, the gophercloud/utils lib uses user.CurrentUser to load get the
user home dir. This fails with a panic error when used in environments
where such functionality is not available.

Let's set the USER env var for now until I fix this issue in
gophercloud.

[flaper87]

/cc @sallyom

[wking]

More on this issue in a different context here and in #1185. Should you set HOME too?

[flaper87]

@wking Thanks! I added HOME although I don't think I need it for this specific fix.

[flaper87]

@wking done! Thanks a bunch for the review 😃

[wking]

/lgtm

[openshift-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: flaper87, wking

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:

• ci-operator/templates/openshift/installer/OWNERS [wking]

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]

@flaper87: Updated the prow-job-cluster-launch-installer-e2e configmap using the following files:

• key cluster-launch-installer-e2e.yaml using file ci-operator/templates/openshift/installer/cluster-launch-installer-e2e.yaml

Details

In response to this:

Sadly, the gophercloud/utils lib uses user.CurrentUser to load get the
user home dir. This fails with a panic error when used in environments
where such functionality is not available.

Let's set the USER env var for now until I fix this issue in
gophercloud.

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.