Bug 2062620 - rendered-master config is missing after install, causing machine-config CO to be stuck
Summary: rendered-master config is missing after install, causing machine-config CO to...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Machine Config Operator
Version: 4.9
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: MCO Bug Bot
QA Contact: Rio Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-10 09:37 UTC by Matt Bargenquast
Modified: 2022-05-24 09:30 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-24 09:30:11 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Matt Bargenquast 2022-03-10 09:37:57 UTC 
Description of problem: 

Installation of an OSD cluster is failing because the machine-config cluster operator remains in a degraded state.

When the cluster is examined, it can be seen that all 3 master nodes have a desired machineconfig which does not exist on the cluster, which is the reason for MCO being degraded.

One distinguishing factor about the cluster is that it was installed with a cluster proxy enabled using a custom installer manifest (https://access.redhat.com/solutions/6063031).

Version-Release number of MCO (Machine Config Operator) (if applicable):

4.9.22

Platform (AWS, VSphere, Metal, etc.): AWS

Are you certain that the root cause of the issue being reported is the MCO (Machine Config Operator)?
Not sure

How reproducible:

QE has reproduced it several times.
Comment 7 Sinny Kumari 2022-05-23 14:59:22 UTC 
Matt, Is this issue still happening? If yes, please provide information needed in  https://bugzilla.redhat.com/show_bug.cgi?id=2062620#c4 .
Note You need to log in before you can comment on or make changes to this bug.