Bug 2100472
| Summary: | TechPreview feature is not enabled, but find "failed to list *v1alpha1.AlertingRule: alertingrules.monitoring.openshift.io is forbidden" in cmo logs | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Junqi Zhao <juzhao> |
| Component: | Monitoring | Assignee: | Simon Pasquier <spasquie> |
| Status: | CLOSED ERRATA | QA Contact: | Junqi Zhao <juzhao> |
| Severity: | medium | Docs Contact: | Brian Burt <bburt> |
| Priority: | medium | ||
| Version: | 4.11 | CC: | anpicker, bburt, spasquie |
| Target Milestone: | --- | ||
| Target Release: | 4.12.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2023-01-17 19:50:29 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: | |
| Bug Depends On: | |||
| Bug Blocks: | 2103127 | ||
|
Description
Junqi Zhao
2022-06-23 13:15:09 UTC
The fix introduces a regression: platform alerts aren't labeled anymore with openshift_io_alert_source="platform". It is being reverted in https://github.com/openshift/cluster-monitoring-operator/pull/1706. The previous PR was a revert, the issue is still present. tested with 4.12.0-0.nightly-2022-07-05-225149, TechPreview feature is not enabled, no errors for alertingrules/alertrelabelconfigs
# oc get featuregate cluster -oyaml
...
spec: {}
# oc -n openshift-monitoring logs -c cluster-monitoring-operator cluster-monitoring-operator-7b6dc644c5-p45jk | grep "alertingrules.monitoring.openshift.io is forbidden"
no result
# oc -n openshift-monitoring logs -c cluster-monitoring-operator cluster-monitoring-operator-7b6dc644c5-p45jk | grep "alertrelabelconfigs.monitoring.openshift.io is forbidden"
no result
and no regression issue like comment 5
# token=`oc create token prometheus-k8s -n openshift-monitoring`
# oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -k -H "Authorization: Bearer $token" 'https://alertmanager-main.openshift-monitoring.svc:9094/api/v2/alerts' | jq
...
"labels": {
"alertname": "Watchdog",
"namespace": "openshift-monitoring",
"openshift_io_alert_source": "platform",
"prometheus": "openshift-monitoring/k8s",
"severity": "none"
}
},
...
"labels": {
"alertname": "AlertmanagerReceiversNotConfigured",
"namespace": "openshift-monitoring",
"openshift_io_alert_source": "platform",
"prometheus": "openshift-monitoring/k8s",
"severity": "warning"
}
}
]
*** Bug 2103033 has been marked as a duplicate of this bug. *** Removing the requires_doc_text because the bug fix has been backported to 4.11.z already (see bug 2103127). 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.12.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:7399 |