Description of problem: There is no PDB for alertmanager, but at the same time there are multiple events about `prometheus-user-workload` PDB being created. Version-Release number of selected component (if applicable): 4.8 How reproducible: always Steps to Reproduce: 1. Start a cluster 2. Check events in openshift-user-workload-monitoring namespace 3. Check PDBs in openshift-monitoring namespace Actual results: There are events about `prometheus-user-workload` PDB and no alertmanager PDB Expected results: There are no events about `prometheus-user-workload` PDB and there is an alertmanager PDB Additional info: Slack thread: https://coreos.slack.com/archives/C0VMT03S5/p1622558281233500
waiting for the fix merged to payload
Test with payload 4.8.0-0.nightly-2021-06-02-025513 PDB alertmanager-main exists and no event about prometheus-user-workload $ oc get pdb -n openshift-monitoring NAME MIN AVAILABLE MAX UNAVAILABLE ALLOWED DISRUPTIONS AGE alertmanager-main N/A 1 1 27m prometheus-adapter 1 N/A 1 25m prometheus-k8s 1 N/A 1 25m $ oc get event |grep poddisruptionbudget/prometheus-user-workload
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