mgr/dashboard: Fix CephPoolGrowthWarning alert

[aaSharma14]

Prometheus reports an error - many-to-many matching not allowed: matching labels must be unique on one side for CephPoolGrowthWarning if we have same pool ids on two different instances.

Fixes: https://tracker.ceph.com/issues/58017
Signed-off-by: Aashish Sharma aasharma@redhat.com

Contribution Guidelines

• To sign and title your commits, please refer to Submitting Patches to Ceph.

• If you are submitting a fix for a stable branch (e.g. "pacific"), please refer to Submitting Patches to Ceph - Backports for the proper workflow.

Checklist

• Tracker (select at least one)
  • References tracker ticket
  • Very recent bug; references commit where it was introduced
  • New feature (ticket optional)
  • Doc update (no ticket needed)
  • Code cleanup (no ticket needed)
• Component impact
  • Affects Dashboard, opened tracker ticket
  • Affects Orchestrator, opened tracker ticket
  • No impact that needs to be tracked
• Documentation (select at least one)
  • Updates relevant documentation
  • No doc update is appropriate
• Tests (select at least one)
  • Includes unit test(s)
  • Includes integration test(s)
  • Includes bug reproducer
  • No tests

Show available Jenkins commands

• jenkins retest this please
• jenkins test classic perf
• jenkins test crimson perf
• jenkins test signed
• jenkins test make check
• jenkins test make check arm64
• jenkins test submodules
• jenkins test dashboard
• jenkins test dashboard cephadm
• jenkins test api
• jenkins test docs
• jenkins render docs
• jenkins test ceph-volume all
• jenkins test ceph-volume tox
• jenkins test windows

[Pegonzal]

Hey @aaSharma14 , the commit isn't signed

[nizamial09]

@aaSharma14 can you add a tracker for it? also could you explain in the description why the error happened and how the fix actually fixed the issue? (not clearly understanding since i've no clue in monitoring queries).

[epuertat]

@aaSharma14 can you add a tracker for it? also could you explain in the description why the error happened and how the fix actually fixed the issue? (not clearly understanding since i've no clue in monitoring queries).

Agree, that's exactly the first thing that came to my mind: what's that "error" and, given it feels like a bug, what releases is this reproduced in?

[nizamial09]

jenkins retest this please

[nizamial09]

@aaSharma14 the signed-off-by check is failing. maybe its because you missed a space after the colon.
Signed-off-by:Aashish Sharma <aasharma@redhat.com>

[aaSharma14]

jenkins test make check

[nizamial09]

jenkins test api

[nizamial09]

jenkins test dashboard