Project

General

Profile

Actions
Copy link

Documentation #24143

closed

strongly warn against custom cluster names

Added by Alfredo Deza almost 8 years ago. Updated 9 months ago.

Status:
Resolved
Priority:
Normal
Assignee:
Zac Dover
Category:
-
Target version:
-
% Done:

0%

Backport:
Reviewed:
Affected Versions:
Pull request ID:
38079
Tags (freeform):
Merge Commit:
3cea1e5a2a73026884b8750cebeb5c17e0ce8d69
Fixed In:
v16.0.0-7509-g3cea1e5a2a
Released In:
v16.2.0~731
Upkeep Timestamp:
2025-07-28T23:40:33+00:00

Description

Users keep tripping on custom cluster name issues, and our docs don't seem to reflect the fact that we are trying to move away from them.

A thorough description in a section that can be used with :ref: would be ideal to link back on other places that might be using "--cluster"

Actions
Copy link
 #1

Updated by Anthony D'Atri over 5 years ago

This is already partly addressed by https://github.com/ceph/ceph/pull/34188

I have entered https://github.com/ceph/ceph/pull/38079 to expand the above, which should fulfill this issue and allow it to be closed. I wanted to assign it to me, but I don't have the juice.

Actions
Copy link
 #2

Updated by Zac Dover 10 months ago

  • Status changed from New to Resolved
  • Assignee set to Zac Dover
  • Pull request ID set to 38079

I have the juice, and now I know that this tracker exists. So I'll mark this resolved, because 38079 resolves this tracker.

Actions
Copy link
 #3

Updated by Upkeep Bot 9 months ago

  • Merge Commit set to 3cea1e5a2a73026884b8750cebeb5c17e0ce8d69
  • Fixed In set to v16.0.0-7509-g3cea1e5a2a
  • Released In set to v16.2.0~731
  • Upkeep Timestamp set to 2025-07-28T23:40:33+00:00
Actions
Copy link

Also available in: Atom PDF