Actions
Bug #55088
closedManager is failing to keep updated metadata in daemon_state for upgraded MON(s) and takes unpredictable time to get correct metadata.
% Done:
0%
Source:
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
rados
Component(RADOS):
Manager (RADOS bits)
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
The ceph manager updates mon metadata through handle_mon_map which gets triggered
less frequently, mostly in the case of addition/removal of MONs or on mgr restart or mgr failover.
The daemon_state still holds old metadata for upgraded mon which is being incorrectly reflected in prometheus metrics.
Updated by Prashant D about 2 years ago
- Status changed from New to Fix Under Review
- Pull request ID set to 45670
Updated by Yuri Weinstein about 2 years ago
Updated by Prashant D about 2 years ago
- Status changed from Fix Under Review to Pending Backport
Updated by Backport Bot about 2 years ago
- Copied to Backport #55305: quincy: Manager is failing to keep updated metadata in daemon_state for upgraded MON(s) and takes unpredictable time to get correct metadata. added
Updated by Prashant D about 2 years ago
- Backport changed from quincy to pacific,quincy
Updated by Backport Bot about 2 years ago
- Copied to Backport #55308: pacific: Manager is failing to keep updated metadata in daemon_state for upgraded MON(s) and takes unpredictable time to get correct metadata. added
Updated by Prashant D over 1 year ago
- Copied to Bug #57678: Mon fail to send pending metadata through MMgrUpdate after an upgrade resulting in prometheus metrics showing old ceph version for upgraded mon added
Updated by Prashant D over 1 year ago
- Copied to deleted (Bug #57678: Mon fail to send pending metadata through MMgrUpdate after an upgrade resulting in prometheus metrics showing old ceph version for upgraded mon)
Updated by Radoslaw Zarzynski about 1 year ago
- Status changed from Pending Backport to Resolved
Actions