Bug 1798945

Summary: bootstrap is never completed upon waiting for some etcd operator
Product: OpenShift Container Platform Reporter: Johnny Liu <jialiu>
Component: EtcdAssignee: Sam Batschelet <sbatsche>
Status: CLOSED CURRENTRELEASE QA Contact: ge liu <geliu>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: ademicev, anusaxen, ashworth, huirwang, isaic, jiajliu, krapohl, scuppett, skolicha, wsun, xtian, yanyang
Target Milestone: ---Keywords: Regression
Target Release: 4.4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-11 20:06:27 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:
Bug Depends On:    
Bug Blocks: 1793115, 1804482    

Comment 3 liujia 2020-02-10 03:54:08 UTC
For upi/vsphere ci test, we have a high ratio reproduce but not 100% to hit the same issue.

Comment 9 Johnny Liu 2020-02-19 13:00:02 UTC
Reproduce again in today's upi on baremetal install - 4.4.0-0.nightly-2020-02-18-233330 + rhcos-44.81.202001241431.0 as boot image

Comment 11 isaic 2020-02-20 13:26:33 UTC
@ jiajliu thanks for the update.  This means we should be using rhcos-44.81.202001241431.0 as boot image, NOT this "newer" dated version rhcos-44.81.202002071430-0-vmware.x86_64.ova?

Comment 12 liujia 2020-02-21 02:15:41 UTC
(In reply to isaic from comment #11)
> @ jiajliu thanks for the update.  This means we should be using
> rhcos-44.81.202001241431.0 as boot image, NOT this "newer" dated version
> rhcos-44.81.202002071430-0-vmware.x86_64.ova?

Yes, currently only rhcos-44.81.202001241431.0 can be used on vsphere as boot image since rhcos-44.81.202002071430-0-vmware.x86_64.ova is broken. btw, upstream has reverted 44.81.202002071430-0 in https://github.com/openshift/installer/commit/1951df7e4e057a0a6e233cafaf87c0379fce900c

Comment 13 isaic 2020-02-21 13:48:18 UTC
Ok thanks for confirming.  Looking forward to hearing back that this issue is resolved as we have a lot of interest in OCP 4.4 deployed on VMware.

Comment 14 liujia 2020-02-24 03:30:08 UTC
Still hit it on upi/vsphere with 4.4.0-0.nightly-2020-02-23-191320.

Comment 15 Joseph Callen 2020-02-24 13:49:36 UTC
*** Bug 1804482 has been marked as a duplicate of this bug. ***

Comment 16 huirwang 2020-02-25 07:11:13 UTC
Hit it on upi/baremetal 4.4.0-0.nightly-2020-02-24-234903

Comment 17 isaic 2020-02-28 18:36:11 UTC
Still not fixed? Any ETA? tks

Comment 18 krapohl 2020-03-03 14:00:29 UTC
Can we get an ETA? This one has been sitting for a long time!

Comment 19 Johnny Liu 2020-03-06 07:15:55 UTC
Per our recently testing, if we launch 3 masters (before QE is using one single master for testing), vsphere upi install will get passed. So remove "testblocker" keyword.

Comment 22 liujia 2020-03-10 02:44:10 UTC
Still hit the same error when trigger upi/baremetal with 3 masters+2 workers. 4.4.0-0.nightly-2020-03-04-204900