-
Bug
-
Resolution: Done-Errata
-
Normal
-
4.15, 4.16
Description of problem:
The olm-operator pod has initilization errors in the logs in a HyperShift deployment. It appears that the --writePackageServerStatusName="" passed in as an argument is being interpreted as \"\" instead of an empty string.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
$ kubectl -n master-coh67vr100a3so6e7erg logs olm-operator-75474cfd48-w2fp5
Actual results:
Several errors that look like this time="2024-04-19T12:41:32Z" level=error msg="initialization error - failed to ensure name=\"\" - ClusterOperator.config.openshift.io \"\\\"\\\"\" is invalid: metadata.name: Invalid value: \"\\\"\\\"\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')" monitor=clusteroperator
Expected results:
No errors
Additional info:
- blocks
-
OCPBUGS-32715 OLM logs contain initialization errors in HyperShift
- Closed
- is cloned by
-
OCPBUGS-32715 OLM logs contain initialization errors in HyperShift
- Closed
- links to
-
RHEA-2024:0041 OpenShift Container Platform 4.16.z bug fix update