-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.21, 4.22
-
Quality / Stability / Reliability
-
False
-
-
5
-
Moderate
-
Yes
-
None
-
None
-
MCO Sprint 281
-
1
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When a empty pull-secret is configured in the cluster, the machine-config ClusterOperator reports a degraded status
$ oc get co machine-config
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
machine-config 4.21.0-0.nightly-2025-10-08-053134 True False True 46m Failed to resync 4.21.0-0.nightly-2025-10-08-053134 because: failed to merge global pull secret: dockerconfig bytes contain JSON null
Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.21.0-0.nightly-2025-10-08-053134 True False 22m Error while reconciling 4.21.0-0.nightly-2025-10-08-053134: the cluster operator machine-config is degraded
How reproducible:
Always
Steps to Reproduce:
1. Configure an empty pull-secret in the cluster
$ oc -n openshift-config set data secret/pull-secret '.dockerconfigjson={}'
Actual results:
The machine-config ClusterOperator will report a degradation
$ oc get co machine-config
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
machine-config 4.21.0-0.nightly-2025-10-08-053134 True False True 46m Failed to resync 4.21.0-0.nightly-2025-10-08-053134 because: failed to merge global pull secret: dockerconfig bytes contain JSON null
Expected results:
MCO should be able to handle an empty pull-secret without problems
Additional info:
Problems related to using an empty pull-secret were previously reported and fixed in https://issues.redhat.com/browse/OCPBUGS-4049
