Bug 1920569
| Summary: | "duplicate series for match group" on PVC scrape | ||||||
|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Sri Ramanujam <sricharan.ramanujam> | ||||
| Component: | Monitoring | Assignee: | Sergiusz Urbaniak <surbania> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | Junqi Zhao <juzhao> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.6 | CC: | alegrand, anpicker, dgrisonn, erooth, kakkoyun, lcosic, mloibl, pkrupa, surbania | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| 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: | 2021-01-26 16:20:30 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: | |||||||
| Attachments: |
|
||||||
Thank you for the report, this seems to be a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1903464. *** This bug has been marked as a duplicate of bug 1903464 *** |
Created attachment 1750919 [details] example warning log of rule failure Description of problem: It seems that I have metrics for the same PVC from multiple worker nodes, and this is causing Prometheus to fail processing the rule due to "many-to-many matching not allowed: matching labels must be unique on one side". This, in turn, is causing an alert to fire. It only seems that one particular PVC is causing this alert. Perhaps it is something about how it is being deployed or used? Version-Release number of selected component (if applicable): 4.6 How reproducible: I'm not sure how reproducible it is, as I'm not sure how it got into this situation to begin with. I deployed a fresh cluster with fresh workloads, and a few minutes later, this alert began to fire. Steps to Reproduce: 1. Deploy workload with PVC to cluster Actual results: Alert begins firing that Prometheus failed to evaluate rules Expected results: Prometheus successfully evaluates all rules