machine-config operator does not initialize #1129
rimvydukas
started this conversation in
General
Replies: 1 comment 6 replies
-
Looks similar to #963, could you attach a log bundle from failed installation? |
Beta Was this translation helpful? Give feedback.
6 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Describe the bug
I did three installations with the latest OKD release and on two of these, the machine-config operatore did not initialize:
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
machine-config False True True 72m Cluster not available for 4.9.0-0.okd-2022-02-12-140851
NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE
master False True True 3 0 0 3 90m
Version
4.9.0-0.okd-2022-02-12-140851
vSphere UPI
How reproducible
It seems that this is happening on every installation.
I need help with the advice - is it a bug and how can I fix it? I'm quite a newbie with OKD, so sorry if I've missed some required info.
Beta Was this translation helpful? Give feedback.
All reactions