Backport #44735
nautilus: prometheus metrics wrongly reports scrubbing pgs
Related issues
History
#1 Updated by Konstantin Shalygin about 4 years ago
- Copied from Bug #44590: prometheus metrics wrongly reports scrubbing pgs added
#2 Updated by Konstantin Shalygin about 4 years ago
- Description updated (diff)
- Status changed from New to In Progress
- Assignee set to Konstantin Shalygin
#3 Updated by Kefu Chai about 4 years ago
- Status changed from In Progress to Resolved
#4 Updated by Nathan Cutler almost 4 years ago
- Target version set to v14.2.9
This update was made using the script "backport-resolve-issue".
backport PR https://github.com/ceph/ceph/pull/34162
merge commit 62afb915ecd67f352966d3175ac7250633a60134 (v14.2.8-257-g62afb915ecd)
#5 Updated by Thore K almost 4 years ago
Why does this issue persist in 14.2.9?
#6 Updated by Nathan Cutler almost 4 years ago
- Target version changed from v14.2.9 to v14.2.10
Why does this issue persist in 14.2.9?
Because 14.2.9 was a "hotfix" release whose only purpose was to patch two CVEs:
https://ceph.io/releases/v14-2-9-nautilus-released/
(The script populates the "Target version" field based on the "git describe" output of the PR merge commit, which in this case is "v14.2.8-257-g62afb915ecd".)
#7 Updated by Thore K almost 4 years ago
Thank you for the clarification. Got confused by the target version.
Still a bit bitter, that we are almost three months in with a backported bug rendering pg alerts useless and telemetry horribly broken as well.
#8 Updated by Nathan Cutler almost 4 years ago
Thore K wrote:
Thank you for the clarification. Got confused by the target version.
Still a bit bitter, that we are almost three months in with a backported bug rendering pg alerts useless and telemetry horribly broken as well.
@Thore - I'm not sure I understand your message here. Are you saying that this backport did not fix Bug #44590 "prometheus metrics wrongly reports scrubbing pgs" in nautilus? Or are you saying the backport introduced another bug? If it's the latter, where was the bug reported/where is it tracked?
#9 Updated by Nathan Cutler almost 4 years ago
Ah, nevermind. I believe you are calling attention to the fact that v14.2.10 is not released yet. We're working on that.