Bug #47334
mgr/dashboard: many-to-many matching not allowed: matching labels must be unique on one side
% Done:
0%
Source:
Tags:
Backport:
octopus nautilus
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature:
Tags:
Description
In the "Host Details" Grafana dashboard, errors for example on "OSD Disk Performance Statistics" tab are seen:
many-to-many matching not allowed: matching labels must be unique on one side
Request details Url api/datasources/proxy/1/api/v1/query_range?query=(irate(node_disk_writes_completed%7Binstance%3D~%22(neptun).*%22%7D%5B5m%5D)%20or%20irate(node_disk_writes_completed_total%7Binstance%3D~%22(neptun).*%22%7D%5B5m%5D))%20*%20on(instance%2C%20device)%20group_left(ceph_daemon)%20label_replace(label_replace(ceph_disk_occupation%2C%20%22device%22%2C%20%22%241%22%2C%20%22device%22%2C%20%22%2Fdev%2F(.*)%22)%2C%20%22instance%22%2C%20%22%241%22%2C%20%22instance%22%2C%20%22(%5B%5E%3A.%5D*).*%22)&start=1597239675&end=1597243290&step=15 Method GET X-Grafana-Org-Id 1 Accept application/json, text/plain, */*
Related issues
History
#1 Updated by Patrick Seidensal about 1 month ago
- Backport changed from nautilus to octopus nautilus
#2 Updated by Patrick Seidensal about 1 month ago
- Pull request ID set to 37023
#3 Updated by Patrick Seidensal about 1 month ago
- Status changed from In Progress to Fix Under Review
#4 Updated by Lenz Grimmer about 1 month ago
- Tags set to grafana, monitoring
- Status changed from Fix Under Review to Pending Backport
- Target version set to v16.0.0
- Tags deleted (
monitoring grafana)
#5 Updated by Nathan Cutler about 1 month ago
- Copied to Backport #47546: nautilus: mgr/dashboard: many-to-many matching not allowed: matching labels must be unique on one side added
#6 Updated by Nathan Cutler about 1 month ago
- Copied to Backport #47547: octopus: mgr/dashboard: many-to-many matching not allowed: matching labels must be unique on one side added
#7 Updated by Nathan Cutler 21 days ago
- Status changed from Pending Backport to Resolved
While running with --resolve-parent, the script "backport-create-issue" noticed that all backports of this issue are in status "Resolved" or "Rejected".