Project

General

Profile

Actions
Copy link

Bug #57317

closed

use actual monitor addresses when creating a peer bootstrap token

Added by Ilya Dryomov over 1 year ago. Updated over 1 year ago.

Status:
Resolved
Priority:
Normal
Assignee:
Ilya Dryomov
Target version:
-
% Done:

0%

Source:
Tags:
backport_processed
Backport:
pacific,quincy
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
47835
Crash signature (v1):
Crash signature (v2):

Description

Relying on mon_host config option is fragile, as the user may confuse v1 and v2 addresses, group them incorrectly, etc.

Related issues 2 (0 open — 2 closed)

Copied to rbd - Backport #57351: pacific: use actual monitor addresses when creating a peer bootstrap tokenResolvedIlya DryomovActions
Copied to rbd - Backport #57352: quincy: use actual monitor addresses when creating a peer bootstrap tokenResolvedIlya DryomovActions
Actions
Copy link
 #1

Updated by Ilya Dryomov over 1 year ago

  • Status changed from In Progress to Fix Under Review
  • Pull request ID set to 47835
Actions
Copy link
 #2

Updated by Ilya Dryomov over 1 year ago

  • Status changed from Fix Under Review to Pending Backport
Actions
Copy link
 #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
Actions
Copy link
 #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
Actions
Copy link
 #5

Updated by Backport Bot over 1 year ago

  • Tags set to backport_processed
Actions
Copy link
 #6

Updated by Backport Bot over 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".

Actions
Copy link

Also available in: Atom PDF