Bug 2089224
Summary: | openshift-monitoring/cluster-monitoring-config configmap always revert to default setting | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
Component: | HyperShift | Assignee: | aaleman |
Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 4.11 | CC: | aaleman, amuller, anpicker, calfonso, cewong, jmarcal, sjenning |
Target Milestone: | --- | ||
Target Release: | 4.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | If docs needed, set a value | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-10 11:13:27 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Junqi Zhao
2022-05-23 09:21:08 UTC
I think this is a bug for HyperShift folks as this is not a problem of CMO but of the HyperShift controller as CMO does not reset values in any condition unless the ConfigMap is removed. I suspect something with https://github.com/openshift/hypershift/blob/9fba0b6ed55808f86b1f9d5d13d2837cf5107b5e/control-plane-operator/hostedclusterconfigoperator/controllers/resources/monitoring/config.go#L20 This is definitely a bug in our reconciliation code. However, instead of fixing the reconciliation code, we should remove any reconciliation of the config. @jmarcal if the CMO can default the prometheus operator deployment node selector to not include master when running inside a cluster with a hosted control plane, then we can leave the config as something entirely modified by the user, which is the case with standalone OCP. Just to remove the needinfo and to make things more traceable, in the CMO PR https://github.com/openshift/cluster-monitoring-operator/pull/1679 we changed the default prometheus operator deployment node selector to not include master when running inside a cluster with a hosted control plane fix is in 4.11.0-0.nightly-2022-06-15-161625 and configmap could reloaded based on change (In reply to Junqi Zhao from comment #8) > fix is in 4.11.0-0.nightly-2022-06-15-161625 and configmap could reloaded > based on change ignore, paste to this bug wrongly tested 4.11.0-0.nightly-2022-06-15-222801 hypershift cluster with Guest cluster kubeconfig, default configmap cluster-monitoring-config is removed # oc -n openshift-monitoring get cm cluster-monitoring-config Error from server (NotFound): configmaps "cluster-monitoring-config" not found followed steps in Comment 0, we can configure monitoring now # oc -n openshift-monitoring get pvc NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE prometheus-prometheus-k8s-0 Bound pvc-303fc231-2d44-4810-a49d-b7a510743d7e 10Gi RWO gp2 9m57s # oc -n openshift-monitoring get pod prometheus-k8s-0 -oyaml | grep persistentVolumeClaim -A1 persistentVolumeClaim: claimName: prometheus-prometheus-k8s-0 Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Important: OpenShift Container Platform 4.11.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-2022:5069 |