Bug 1759299

Description of problem:

The release-openshift-openshift-ansible-e2e-aws-scaleup-rhel7-4.2 is failing consistently in CI: https://prow.svc.ci.openshift.org/view/gcs/origin-ci-test/logs/release-openshift-openshift-ansible-e2e-aws-scaleup-rhel7-4.2/47


The failure from the web interface looks like:

```
2019/10/07 13:51:47 Importing release image latest
2019/10/07 13:57:00 Ran for 5m22s
2019/10/07 13:57:00 Submitted failure event to sentry (id=6ad46e06cb844b7e9d8e035f85ede183)
error: could not run steps: step [release:latest] failed: the following tags from the release could not be imported to stable after five minutes: aws-machine-controllers, azure-machine-controllers, baremetal-installer, baremetal-machine-controllers, baremetal-operator, baremetal-runtimecfg, cli, cli-artifacts, cloud-credential-operator, cluster-authentication-operator, cluster-autoscaler, cluster-autoscaler-operator, cluster-bootstrap, cluster-config-operator, cluster-dns-operator, cluster-image-registry-operator, cluster-ingress-operator, cluster-kube-apiserver-operator, cluster-kube-controller-manager-operator, cluster-kube-scheduler-operator, cluster-machine-approver, cluster-monitoring-operator, cluster-network-operator, cluster-node-tuned, cluster-node-tuning-operator, cluster-openshift-apiserver-operator, cluster-openshift-controller-manager-operator, cluster-samples-operator, cluster-storage-operator, cluster-svcat-apiserver-operator, cluster-svcat-controller-manager-operator, cluster-update-keys, cluster-version-operator, configmap-reloader, console, console-operator, container-networking-plugins, coredns, deployer, docker-builder, docker-registry, etcd, gcp-machine-controllers, grafana, haproxy-router, hyperkube, insights-operator, installer, installer-artifacts, ironic, ironic-inspector, ironic-ipa-downloader, ironic-rhcos-downloader, ironic-static-ip-manager, jenkins, jenkins-agent-maven, jenkins-agent-nodejs, k8s-prometheus-adapter, keepalived-ipfailover, kube-client-agent, kube-etcd-signer-server, kube-proxy, kube-rbac-proxy, kube-state-metrics, kuryr-cni, kuryr-controller, libvirt-machine-controllers, local-storage-static-provisioner, machine-api-operator, machine-config-operator, machine-os-content, mdns-publisher, multus-admission-controller, multus-cni, must-gather, node, oauth-proxy, oauth-server, openshift-apiserver, openshift-controller-manager, openshift-state-metrics, openstack-machine-controllers, operator-lifecycle-manager, operator-marketplace, operator-registry, ovn-kubernetes, pod, prom-label-proxy, prometheus, prometheus-alertmanager, prometheus-config-reloader, prometheus-node-exporter, prometheus-operator, sdn-controller, service-ca-operator, service-catalog, telemeter, tests

```

A chat with @clayton and @stevekuznetsov revealed that there was an error in the imagestream:

```
                "message": "you may not have access to the Docker image \"http://quay.io/openshift-release-dev/ocp-v4.0-art
dev@sha256:24e8245810a1f1738ef2185b292a1e8a2f590f58311c565892156a3f6a4d7ba7\
(quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:24e8245810a1f1738ef2185b292a1e8a2f590f58311c565892156a3f6a4d7ba7\)""

```

Conversation from clayton and steve:

```
14:19:01 stevekuznetsov | well @vrutkovs you should fix that in the job
14:19:09 stevekuznetsov | it's 4.2
14:19:11 stevekuznetsov | and on every image
14:19:19 stevekuznetsov | so i think the author just doesnt mount the pull secret
14:19:35        clayton | any CI image stream gets the pull secret that lets you pull those
14:19:40        clayton | so i doubt it?s that unless the job is super hacky and wierd
14:21:16 stevekuznetsov | ive nver looked at it so i dont know
14:21:31 stevekuznetsov | only that job is broken so i am inclined to assume that it is
```