Description of problem: Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
Verified on 4.9.0-0.nightly-2021-11-04-020704. Verification steps: 1. Disable cluster-monitoring-operator: merge=$(cat <<-__EOF { "spec": { "overrides": [ [ .spec | .? | .overrides[] | .? | select(.name != "cluster-monitoring-operator")] + [{ "group": "apps/v1", "kind": "Deployment", "name": "cluster-monitoring-operator", "namespace": "openshift-monitoring", "unmanaged": true }] ] | flatten } } __EOF ) overrides=$(oc get clusterversion version -o json | jq "$merge") oc patch clusterversion/version --type=merge -p="$overrides" oc scale --replicas=0 deployment/cluster-monitoring-operator -n openshift-monitoring 2. Disable prometheus-operator oc scale --replicas=0 deployment/prometheus-operator -n openshift-monitoring 3. Adjust "APIRemovedInNextEUSReleaseInUse" rule in "prometheus-k8s-rulefiles-0" config map to trigger it 4. Restart "prometheus-k8s" stateful set oc scale --replicas=0 statefulset/prometheus-k8s -n openshift-monitoring oc scale --replicas=2 statefulset/prometheus-k8s -n openshift-monitoring 5. Wait until the alert will be firing. You can check it in Prometheus UI: https://prometheus-k8s-openshift-monitoring.apps.<cluster hostname> 6. Restart the Insights Operator 7. Wait until the archive will be created 8. Download and check the content of the archive. The archive should content conditional/alerts/APIRemovedInNextEUSReleaseInUse/api_request_counts.json file
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 (OpenShift Container Platform 4.9.6 bug fix 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/RHBA-2021:4119