-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.12.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Low
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
There are errors logged by the OSUS Operator, like:
1.7562266062879949e+09 ERROR controller_updateservice GraphDataPodStatusEmpty {"Request.Namespace": "openshift-update-service", "Request.Name": "sample", "error": "Graph-Data pod returned empty container status"}
github.com/openshift/cincinnati-operator/controllers.handleErr
/remote-source/app/controllers/updateservice_controller.go:214
github.com/openshift/cincinnati-operator/controllers.(*UpdateServiceReconciler).ensureGraphDataSHA
/remote-source/app/controllers/updateservice_controller.go:424
github.com/openshift/cincinnati-operator/controllers.(*UpdateServiceReconciler).Reconcile
/remote-source/app/controllers/updateservice_controller.go:173
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:121
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:320
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:273
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
/remote-source/app/vendor/sigs.k8s.io/controller-runtime/pkg/internal/controller/controller.go:234
Version-Release number of selected component (if applicable):
5.0.3
How reproducible:
Seems often
Steps to Reproduce:
1. Deploy an UpdateService with the operator and let it run for some time
2. Inspect the operator log
Actual results:
Errors in the log
Expected results:
No such errors in the log
Additional info:
This is probably not that serious because in controller-runtime returning an error will cause the controller to retry, but I would not expect a healthy operator to emit error noise in its log (at minimum it gets in the way when troubleshooting).