Bug 1779196
Summary: | vSphere UPI: failed to initialize the cluster: Some cluster operators are still updating: authentication, console | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Anoel Yakoubov <ayakoubo> |
Component: | Image Registry | Assignee: | Oleg Bulatov <obulatov> |
Status: | CLOSED DUPLICATE | QA Contact: | Wenjing Zheng <wzheng> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.2.z | CC: | aos-bugs, jokerman, kgarriso |
Target Milestone: | --- | ||
Target Release: | 4.4.0 | ||
Hardware: | x86_64 | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2019-12-19 10:48:42 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
Anoel Yakoubov
2019-12-03 13:49:52 UTC
moving to machine-config as it's one of the failing operator. Hi, I am not so understand which info you need me to provide? Please elaborate little bit more! @Anoel: please attach the logs using this tool: https://github.com/openshift/must-gather Hi, I uploaded the tar file with all logs to the Google drive You can find it in the next link https://drive.google.com/file/d/1nCmomYoInn0SWY0dcsmaOV0Te-_UykNz/view?usp=sharing Looking at the machineconfig pools both master and worker aren't degraded: degradedMachineCount: 0 machineCount: 3 observedGeneration: 2 readyMachineCount: 3 unavailableMachineCount: 0 updatedMachineCount: 3 degradedMachineCount: 0 machineCount: 2 observedGeneration: 2 readyMachineCount: 2 unavailableMachineCount: 0 updatedMachineCount: 2 MCO is also fine: conditions: - lastTransitionTime: 2019-12-18T07:01:48Z message: Cluster has deployed 4.2.4 status: "True" type: Available - lastTransitionTime: 2019-12-18T07:01:48Z message: Cluster version is 4.2.4 status: "False" type: Progressing - lastTransitionTime: 2019-12-18T07:00:35Z status: "False" type: Degraded - lastTransitionTime: 2019-12-18T07:01:48Z reason: AsExpected status: "True" type: Upgradeable I issue that I do see is: conditions: - lastTransitionTime: 2019-12-18T06:58:59Z status: "False" type: Available - lastTransitionTime: 2019-12-18T07:19:24Z message: Cluster operator image-registry is still updating reason: ClusterOperatorNotAvailable status: "True" type: Failing - lastTransitionTime: 2019-12-18T06:58:59Z message: 'Unable to apply 4.2.4: the cluster operator image-registry has not yet successfully rolled out' reason: ClusterOperatorNotAvailable status: "True" type: Progressing Reassigning: Image-Registry, PTAL *** This bug has been marked as a duplicate of bug 1770658 *** Why I am still receiving email every day with this outstanding request? [Red Hat Bugzilla] Your Outstanding Requests Inbox x bugzilla 4:24 AM (6 hours ago) to me The following is a list of bugs or attachments to bugs in which a user has been waiting more than 3 days for a response from you. Please take action on these requests as quickly as possible. (Note that some of these bugs might already be closed, but a user is still waiting for your response.) We'll remind you again tomorrow if these requests are still outstanding, or if there are any new requests where users have been waiting more than 3 days for your response. needinfo -------- Bug 1779196: vSphere UPI: failed to initialize the cluster: Some cluster operators are still updating: authentication, console (19 days old) https://bugzilla.redhat.com/show_bug.cgi?id=1779196 |