Bug #57317
use actual monitor addresses when creating a peer bootstrap token
% Done:
0%
Source:
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Description
Relying on mon_host config option is fragile, as the user may confuse v1 and v2 addresses, group them incorrectly, etc.
Related issues
History
#1 Updated by Ilya Dryomov over 1 year ago
- Status changed from In Progress to Fix Under Review
- Pull request ID set to 47835
#2 Updated by Ilya Dryomov over 1 year ago
- Status changed from Fix Under Review to Pending Backport
#3 Updated by Backport Bot over 1 year ago
- Copied to Backport #57351: pacific: use actual monitor addresses when creating a peer bootstrap token added
#4 Updated by Backport Bot over 1 year ago
- Copied to Backport #57352: quincy: use actual monitor addresses when creating a peer bootstrap token added
#5 Updated by Backport Bot over 1 year ago
- Tags set to backport_processed
#6 Updated by Backport Bot about 1 year 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".