Description of problem:
Bootstraping a GCP 4.5 cluster in shared VPC fails recently.
Version-Release number of the following components:
Steps to Reproduce:
1. Install a GCP cluster in shared VPC
Installation is successful
May 20 12:17:01 yy4-f7r26-bootstrap.c.openshift-qe.internal bootkube.sh: Starting temporary bootstrap control plane...
May 20 12:17:01 yy4-f7r26-bootstrap.c.openshift-qe.internal bootkube.sh: E0520 12:17:01.386322 1 reflector.go:134] github.com/openshift/cluster-bootstrap/pkg/start/status.go:66: Failed to list *v1.Pod: Get https://localhost:6443/api/v1/pods: dial tcp [::1]:6443: connect: connection refused
May 20 12:17:01 yy4-f7r26-bootstrap.c.openshift-qe.internal bootkube.sh: [#1] failed to fetch discovery: Get https://localhost:6443/api?timeout=32s: dial tcp [::1]:6443: connect: connection refused
Created attachment 1690515 [details]
In your description, you said bootstrapping fails "recently". Does this indicate you had it working with a version prior to 4.5.0-0.nightly-2020-05-20-053050? I'm trying the same version using my XPN script to see if I can reproduce.
The issue does not always but often happen. It sometimes works with 4.5.0-0.nightly-2020-05-18-225907 and sometimes fails.
I do not see this error today hence remove testblocker keyword.
It looks like the cluster failed to properly configure the pause image.
May 21 03:00:59 yy4-f7r26-bootstrap.c.openshift-qe.internal crio: time="2020-05-21 03:00:59.190732656Z" level=warning msg="imageStatus: can't find k8s.gcr.io/pause:3.1" id=9ed10c1f-21df-452b-b7a2-e4d4e772f1aa
Created attachment 1694987 [details]
bootstrap log tarball
Created attachment 1697753 [details]
Moving to ON_QA since we think this should be fixed after the cluster id changes and using a nat with auto mode.
Experienced pull image failure on worker node 2/5 times with 4.6.0-0.nightly-2020-07-14-035247. I'm not sure if there's something wrong with quay.io. I'll keep monitoring it.
$ systemctl status machine-config-daemon-pull.service
● machine-config-daemon-pull.service - Machine Config Daemon Pull
Loaded: loaded (/etc/systemd/system/machine-config-daemon-pull.service; enabled; vendor preset: enabled)
Active: failed (Result: exit-code) since Tue 2020-07-14 07:34:14 UTC; 1h 0min ago
Process: 1680 ExecStart=/bin/sh -c /usr/bin/podman pull --authfile=/var/lib/kubelet/config.json --quiet 'quay>
Process: 1665 ExecStart=/bin/sh -c /bin/mkdir -p /run/bin && chcon --reference=/usr/bin /run/bin (code=exited>
Main PID: 1680 (code=exited, status=125)
Jul 14 07:33:39 yyxpn12-gq4xq-w-a-0.c.openshift-qe.internal systemd: Starting Machine Config Daemon Pull...
Jul 14 07:34:14 yyxpn12-gq4xq-w-a-0.c.openshift-qe.internal sh: Error: error pulling image "quay.io/opens>
Jul 14 07:34:14 yyxpn12-gq4xq-w-a-0.c.openshift-qe.internal systemd: machine-config-daemon-pull.service: Mai>
Jul 14 07:34:14 yyxpn12-gq4xq-w-a-0.c.openshift-qe.internal systemd: machine-config-daemon-pull.service: Fai>
Jul 14 07:34:14 yyxpn12-gq4xq-w-a-0.c.openshift-qe.internal systemd: Failed to start Machine Config Daemon P>
Jul 14 07:34:14 yyxpn12-gq4xq-w-a-0.c.openshift-qe.internal systemd: machine-config-daemon-pull.service: Con>
It's not reproduced recently. Moving it to verified state.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.