Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1796965

Summary: bootstrap take a long time to completed with cluster-etcd-operator
Product: OpenShift Container Platform Reporter: Alay Patel <alpatel>
Component: EtcdAssignee: Sam Batschelet <sbatsche>
Status: CLOSED ERRATA QA Contact: ge liu <geliu>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 4.4   
Target Milestone: ---   
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-04 11:28:32 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Alay Patel 2020-01-31 16:01:06 UTC 
Description of problem:

1. The cluster-etcd-operator introduced an init container that waits service account(namespace, token, ca.crt, service-ca.crt) related files to be synced to the static pod. The CI runs have indicated takes a long time for service-ca.crt to be synced, even after kube is up. 

2. The cluster-etcd-operator also introduced a new wait-for-ceo[1] command in the installer, that blocks the installer from destroying the bootstrap node before etcd has scaled to all 4 masters. The wait-for-ceo command also needs to wait for kube apiserver to roll out valid config. The loop checking this config errors out without checking all the config. It should collect the errors and attempt to check the config for all kube-apiserver pods.


[1] https://github.com/openshift/installer/blob/993c8cec1e8b1dbf58383fa52b264695187656be/data/data/bootstrap/files/usr/local/bin/bootkube.sh.template#L403
Version-Release number of selected component (if applicable):
Comment 2 ge liu 2020-02-14 04:55:19 UTC 
This issue seems still be hit in installation randomly, https://bugzilla.redhat.com/show_bug.cgi?id=1798945, we may trace this issue with one bug, so close this one, pls correct me if there is misunderstanding.
Comment 4 errata-xmlrpc 2020-05-04 11:28:32 UTC 
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, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:0581