machine-config degraded after installation #1396
Unanswered
sven-borkert
asked this question in
Q&A
Replies: 1 comment 6 replies
-
Dupe of #963 possibly? |
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
-
Hi,
I did an installation with user provisioned infrastructure, according to this documentation:
https://docs.okd.io/latest/installing/installing_platform_agnostic/installing-platform-agnostic.html
Installer reports version: openshift-install 4.11.0-0.okd-2022-11-05-030711
The installation seems to have run without visible problems, but one of the cluster operators does not become happy when I run "watch -n5 oc get clusteroperators":
machine-config True True True 47m Unable to apply 4.11.0-0.okd-2022-11-05-030711: error during syncRequiredMachineConfigPools: [timed out waiting for the condition, error pool master is not ready, retrying. Status: (pool degraded: true total: 3, ready 0, updated: 0, unavailable: 3)]
Cluster settings show that it is trying to update the master nodes, but cannot because machine config pools are degraded:
$ oc get mcp
NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE
master False True True 3 0 0 3 69m
worker rendered-worker-86b9dd586f014e19df80cd351a231f83 True False False 2 2 2 0 69m
$ oc get machineconfigs
NAME GENERATEDBYCONTROLLER IGNITIONVERSION AGE
00-master 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
00-worker 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
01-master-container-runtime 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
01-master-kubelet 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
01-worker-container-runtime 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
01-worker-kubelet 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
99-master-generated-crio-add-inheritable-capabilities 3.2.0 71m
99-master-generated-registries 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
99-master-okd-extensions 3.2.0 82m
99-master-ssh 3.2.0 82m
99-worker-generated-crio-add-inheritable-capabilities 3.2.0 71m
99-worker-generated-registries 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
99-worker-ssh 3.2.0 82m
rendered-master-c8e03707c9787d303379616eca44f8ad 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
rendered-worker-86b9dd586f014e19df80cd351a231f83 0854b1512e8e445c235252a76e42043bbfa67512 3.2.0 71m
The list of pods shows a pod "installer-6-master2.ocp4.borkert.net" has failed. The only visible error in the log of that pod is:
F1108 20:37:05.089596 1 cmd.go:106] Get "https://172.30.0.1:443/api/v1/namespaces/openshift-kube-scheduler/pods?labelSelector=app%3Dinstaller": dial tcp 172.30.0.1:443: connect: connection refused
Machine config pool "master" in the console shows this error:
Could someone please give me a hint what is wrong with the system, or what I have to read to understand this. I could not yet find anything helpful.
Regards,
Sven
Beta Was this translation helpful? Give feedback.
All reactions