-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.16
-
Important
-
No
-
MCO Sprint 250
-
1
-
Rejected
-
False
-
-
N/A
-
Release Note Not Required
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:
- relates to
-
-
- Closed
-
- links to
-
RHEA-2024:0041
OpenShift Container Platform 4.16.z bug fix update
[OCPBUGS-30136] machine-config CO degraded due to MachineConfigNode without ownerReference
Hi cdoern@redhat.com , can you help to check release note field, then we can move this bug to verified.
Sergio Regidor de la Rosa
added a comment - Verified using IPI on GCP version:
$ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.16.0-0.nightly-2024-03-06-073110 True False 6h33m Cluster version is 4.16.0-0.nightly-2024-03-06-073110
Enable techpreview:
oc patch featuregate cluster --type=merge -p '{"spec":{"featureSet": "TechPreviewNoUpgrade"}}'
We can see the machineconfignode resources
$ oc get machineconfignodes NAME UPDATED UPDATEPREPARED UPDATEEXECUTED UPDATEPOSTACTIONCOMPLETE UPDATECOMPLETE RESUMED sregidor-a2-hjfhv-master-0 True False False False False False sregidor-a2-hjfhv-master-1 True False False False False False sregidor-a2-hjfhv-master-2 True False False False False False sregidor-a2-hjfhv-worker-a-cvp64 True False False False False False sregidor-a2-hjfhv-worker-b-c5ll7 True False False False False False
And machine-config CO is not degraded:
$ oc get co machine-config NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE machine-config 4.16.0-0.nightly-2024-03-06-073110 True False False 6h55m
We will be able to move the status to VERIFIED as soon as the Release Notes fields are filled in with the right values.
Sergio Regidor de la Rosa
added a comment - Verified using IPI on GCP version:
$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.16.0-0.nightly-2024-03-06-073110 True False 6h33m Cluster version is 4.16.0-0.nightly-2024-03-06-073110
Enable techpreview:
oc patch featuregate cluster --type=merge -p '{"spec":{"featureSet": "TechPreviewNoUpgrade"}}'
We can see the machineconfignode resources
$ oc get machineconfignodes
NAME UPDATED UPDATEPREPARED UPDATEEXECUTED UPDATEPOSTACTIONCOMPLETE UPDATECOMPLETE RESUMED
sregidor-a2-hjfhv-master-0 True False False False False False
sregidor-a2-hjfhv-master-1 True False False False False False
sregidor-a2-hjfhv-master-2 True False False False False False
sregidor-a2-hjfhv-worker-a-cvp64 True False False False False False
sregidor-a2-hjfhv-worker-b-c5ll7 True False False False False False
And machine-config CO is not degraded:
$ oc get co machine-config
NAME VERSION AVAILABLE PROGRESSING DEGRADED SINCE MESSAGE
machine-config 4.16.0-0.nightly-2024-03-06-073110 True False False 6h55m
We will be able to move the status to VERIFIED as soon as the Release Notes fields are filled in with the right values. 
OpenShift Jira Bot
added a comment - Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified.
OpenShift Jira Bot
added a comment - Hi cdoern@redhat.com ,
Bugs should not be moved to Verified without first providing a Release Note Type("Bug Fix" or "No Doc Update") and for type "Bug Fix" the Release Note Text must also be provided. Please populate the necessary fields before moving the Bug to Verified. 
Since the problem described in this issue should be resolved in a recent advisory, it has been closed.
For information on the advisory (Critical: OpenShift Container Platform 4.16.0 bug fix and security update), and where to find the updated files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2024:0041