Details
-
Bug
-
Resolution: Unresolved
-
Normal
-
4.16
-
Important
-
No
-
MCO Sprint 250
-
1
-
Rejected
-
False
-
-
When populating the ownerReference of a MachineConfigNode object, it is necessary to hardcode the version and type of the Node object since they are not stored in the one we retrieve from the API.
-
Bug Fix
-
In Progress
Description
Description of problem:
$ oc get co machine-config
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
machine-config 4.16.0-0.ci-2024-03-01-110656 False False True 2m56s Cluster not available for [{operator 4.16.0-0.ci-2024-03-01-110656}]: MachineConfigNode.machineconfiguration.openshift.io "ip-10-0-24-212.us-east-2.compute.internal" is invalid: [metadata.ownerReferences.apiVersion: Invalid value: "": version must not be empty, metadata.ownerReferences.kind: Invalid value: "": kind must not be empty]
MCO operator is failing with this error:
218", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Warning' reason: 'MachineConfigNodeFailed' Cluster not available for [{operator 4.16.0-0.ci-2024-03-01-110656}]: MachineConfigNode.machineconfiguration.openshift.io "ip-10-0-24-212.us-east-2.compute.internal" is invalid: [metadata.ownerReferences.apiVersion: Invalid value: "": version must not be empty, metadata.ownerReferences.kind: Invalid value: "": kind must not be empty]
I0301 17:19:12.823035 1 event.go:364] Event(v1.ObjectReference{Kind:"", Namespace:"openshift-machine-config-operator", Name:"machine-config", UID:"c1bad7e7-26ff-47fb-8a2d-a0c03c04d218", APIVersion:"", ResourceVersion:"", FieldPath:""}): type: 'Warning' reason: 'OperatorDegraded: MachineConfigNodeFailed' Failed to resync 4.16.0-0.ci-2024-03-01-110656 because: MachineConfigNode.machineconfiguration.openshift.io "ip-10-0-49-207.us-east-2.compute.internal" is invalid: [metadata.ownerReferences.apiVersion: Invalid value: "": version must not be empty, metadata.ownerReferences.kind: Invalid value: "": kind must not be empty]
Version-Release number of selected component (if applicable):
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.16.0-0.ci-2024-03-01-110656 True False 17m Error while reconciling 4.16.0-0.ci-2024-03-01-110656: the cluster operator machine-config is not available
How reproducible:
Always
Steps to Reproduce:
1. Enable techpreview
oc patch featuregate cluster --type=merge -p '{"spec":{"featureSet": "TechPreviewNoUpgrade"}}'
Actual results:
machine-config CO is degraded
Expected results:
machine-config CO should not be degraded, no error should happen in MCO operator pod
Additional info:
Attachments
Issue Links
- relates to
-
-
- Verified
-
- links to
-
RHEA-2024:0041
OpenShift Container Platform 4.16.z bug fix update
