Description of problem: User Workload Prometheus has an incorrect pod anti-affinity rule. Bug was introduced in https://github.com/openshift/cluster-monitoring-operator/pull/1018 Version-Release number of selected component (if applicable): 4.7 How reproducible: Always Steps to Reproduce: 1. Start a cluster with UWM 2. Check UWM prometheus STS 3. Actual results: PodAntiAffinity section references the in-cluster prometheus Expected results: PodAntiAffinity section references the UWM prometheus and not in-cluster one Additional info:
Test with payload 4.8.0-0.nightly-2021-03-14-134919 # oc -n openshift-user-workload-monitoring get sts prometheus-user-workload -oyaml -- podAntiAffinity: preferredDuringSchedulingIgnoredDuringExecution: - podAffinityTerm: labelSelector: matchExpressions: - key: prometheus operator: In values: - user-workload namespaces: - openshift-user-workload-monitoring --
*** Bug 1937466 has been marked as a duplicate of this bug. ***
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 (Moderate: OpenShift Container Platform 4.8.2 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-2021:2438