-
Bug
-
Resolution: Done
-
Normal
-
None
-
4.16, 4.17
-
Moderate
-
None
-
MCO Sprint 256, MCO Sprint 257
-
2
-
False
-
Description of problem
Current 4.16 and 4.17 clusters with the default feature set will have logs full of noise like:
W0607 19:39:26.236019 1 reflector.go:539] github.com/openshift/client-go/machineconfiguration/informers/externalversions/factory.go:125: failed to list *v1alpha1.MachineOSBuild: the server could not find the requested resource (get machineosbuilds.machineconfiguration.openshift.io) E0607 19:39:26.236052 1 reflector.go:147] github.com/openshift/client-go/machineconfiguration/informers/externalversions/factory.go:125: Failed to watch *v1alpha1.MachineOSBuild: failed to list *v1alpha1.MachineOSBuild: the server could not find the requested resource (get machineosbuilds.machineconfiguration.openshift.io)
as they try to watch MachineOSBuild, despite that type being feature-gated by OnClusterBuild. This informer should only be set up when OnClusterBuild is enabled.
Version-Release number of selected component
4.17.0-ec.0 run has these symptoms.
4.16.0-rc.6 run has these symptoms.
How reproducible
Every time.
Steps to Reproduce
Run any CI with the default feature set. Check machine-config controller logs. In a running cluster, that's:
$ oc -n openshift-machine-config-operator logs -l k8s-app=machine-config-controller -c machine-config-controller
Actual results
Lots of failed to list *v1alpha1.MachineOSBuild: the server could not find the requested resource.
Expected results
No mention of MachineOSBuild.
Additional info
Regressed with MCO-1131 landing this feature.
- causes
-
-
- Verified
-
- relates to
-
MCO-1131 Merge implementation machineOSBuild and machineOSConfig in MCO
-
- Closed
-
- links to
