-
Bug
-
Resolution: Duplicate
-
Critical
-
None
-
4.12
-
None
-
None
-
Proposed
-
False
-
Proxy jobs are broken, failing to bootstrap with errors like this:
./control-plane/10.0.62.3/journals/machine-config-daemon-firstboot.log:Oct 11 00:53:10 ip-10-0-62-3 machine-config-daemon[2133]: W1011 00:53:10.351649 2133 firstboot_complete_machineconfig.go:46] error: failed to update OS to quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0daf5c4a35424410e88dde102022fc3581302bc8a98e09e2e4748502c59b3661 : error running rpm-ostree rebase --experimental ostree-unverified-registry:quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0daf5c4a35424410e88dde102022fc3581302bc8a98e09e2e4748502c59b3661: error: remote error: (Mirrors also failed: [quayio-pull-through-cache-us-east-2-ci.apps.ci.l2s4.p1.openshiftapps.com/openshift-release-dev/ocp-v4.0-art-dev@sha256:0daf5c4a35424410e88dde102022fc3581302bc8a98e09e2e4748502c59b3661: pinging container registry quayio-pull-through-cache-us-east-2-ci.apps.ci.l2s4.p1.openshiftapps.com: Get "https://quayio-pull-through-cache-us-east-2-ci.apps.ci.l2s4.p1.openshiftapps.com/v2/": dial tcp 35.153.154.153:443: i/o timeout]): quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0daf5c4a35424410e88dde102022fc3581302bc8a98e09e2e4748502c59b3661: pinging container registry quay.io: Get "https://quay.io/v2/": dial tcp 50.19.184.112:443: i/o timeout
It appears the cluster proxy settings aren't passed through to rpm-ostree.
Looks like it started around the beginning on October. I set this to blocker but feel free to adjust priority.
job=periodic-ci-openshift-release-master-nightly-4.12-e2e-aws-ovn-proxy=all
- is duplicated by
-
-
- Closed
-
- relates to
-
TRT-608 aws-ovn-proxy appears to be broken
-
- Closed
-
