-
Bug
-
Resolution: Unresolved
-
Minor
-
None
-
4.16.z
-
None
-
Quality / Stability / Reliability
-
False
-
-
None
-
Moderate
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
When installing the OpenShift Update Service Operator from the OpenShift Console has not an option to enable the Monitoring. Enable the monitoring for the namespace `openshift-update-service` is documented when using the CLI as visible in [0]
Version-Release number of selected component (if applicable):
$ oc get csv -n openshift-update-service NAME DISPLAY VERSION REPLACES PHASE update-service-operator.v5.0.3 OpenShift Update Service 5.0.3 update-service-operator.v5.0.2 Succeeded $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.16.0-0.nightly-2025-02-20-065641 True False 134m Cluster version is 4.16.0-0.nightly-2025-02-20-065641
How reproducible:
Always
Steps to Reproduce:
1. Install a cluster with OpenShift 4.16 2. Install the OpenShift Upate Service Operator from the OpenShift Console and verify that a flag for enabling the monitoring for the namespace `openshift-update-service` is not present when installing it
Actual results:
The operator has not a flag for enabling the Monitoring for the OpenShift Update service and the label "openshift.io/cluster-monitoring":"true" is not added by default. For verifying it run the command below: $ oc get ns openshift-update-service -o jsonpath='{.metadata.labels}' -n openshift-update-service
Expected results:
When installing from the OpenShift Console, it should be expected to have a checkbox for enabling the Monitoring for the namespace `openshift-update-service`
Additional info:
The workaround for when installing the Operator from the OpenShift Console is to go to a terminal and add the label "openshift.io/cluster-monitoring":"true" to the namespace `openshift-update-service` running the command: oc label ns/openshift-update-service openshift.io/cluster-monitoring=true