Bug 1798945
Summary: | bootstrap is never completed upon waiting for some etcd operator | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Johnny Liu <jialiu> |
Component: | Etcd | Assignee: | Sam Batschelet <sbatsche> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | ge liu <geliu> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 4.4 | CC: | 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
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 @ 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? (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 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. Still hit it on upi/vsphere with 4.4.0-0.nightly-2020-02-23-191320. *** Bug 1804482 has been marked as a duplicate of this bug. *** Hit it on upi/baremetal 4.4.0-0.nightly-2020-02-24-234903 Still not fixed? Any ETA? tks Can we get an ETA? This one has been sitting for a long time! 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. Still hit the same error when trigger upi/baremetal with 3 masters+2 workers. 4.4.0-0.nightly-2020-03-04-204900 |