-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
4.17.0
-
None
-
Important
-
None
-
False
-
Description of problem:
A node is stuck in MCO rollout. Error logs are attached. Openshift version 4.17.0-rc.5 ODF 4.16 ISF 2.8.1[root@roadiem7 ~]# oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.17.0-rc.5 True False 15d Error while reconciling 4.17.0-rc.5: the cluster operator machine-config is degraded [root@roadiem7 ~]# oc get csv -n ibm-spectrum-fusion-ns NAME DISPLAY VERSION REPLACES PHASE isf-operator.v2.8.2 IBM Storage Fusion 2.8.2 isf-operator.v2.8.1 Succeeded metallb-operator.v4.16.0-202409161407 MetalLB Operator 4.16.0-202409161407 Succeeded [root@roadiem7 ~]# oc get csv -n openshift-storage NAME DISPLAY VERSION REPLACES PHASE mcg-operator.v4.16.1 NooBaa Operator 4.16.1 Succeeded metallb-operator.v4.16.0-202409161407 MetalLB Operator 4.16.0-202409161407 Succeeded ocs-client-operator.v4.16.1 OpenShift Data Foundation Client 4.16.1 Succeeded ocs-operator.v4.16.1 Container Storage 4.16.1 Succeeded odf-csi-addons-operator.v4.16.1 CSI Addons 4.16.1 Succeeded odf-operator.v4.16.1 IBM Storage Fusion Data Foundation 4.16.1 Succeeded odf-prometheus-operator.v4.16.1 Prometheus Operator 4.16.1 Succeeded recipe.v4.16.1 DR Recipe Operator 4.16.1 Succeeded rook-ceph-operator.v4.16.1 IBM Storage Fusion Data Foundation 4.16.1 Succeeded [root@roadiem7 ~]# oc get mcp NAME CONFIG UPDATED UPDATING DEGRADED MACHINECOUNT READYMACHINECOUNT UPDATEDMACHINECOUNT DEGRADEDMACHINECOUNT AGE master rendered-master-e9f8f03cb0534816a8afcae01fa26185 True False False 3 3 3 0 18d worker rendered-worker-c0018729404fa1b0de5150137597acea False True True 5 4 4 1 18d Degraded Reason: could not write image pull secret data to node filesystem: failed to create directory "/etc/mco": mkdir /etc: file exists
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info: