Actions
Bug #52042
closedAfter deployment the example of cephadm shell invocation is overly complex
Status:
Resolved
Priority:
Normal
Assignee:
Category:
cephadm (binary)
Target version:
% Done:
0%
Source:
Tags:
low-hanging-fruit
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Description
If there is only one ceph instance on the host (which is the most likely user scenario), cephadm shell can infer the fsid and pick up the conf/keyring automatically.
In this case where there is only one cluster - why not provide the simple example that is likely to fit most user user cases
i.e just show "cephadm shell"
Updated by Redouane Kachach Elhichou about 2 years ago
Is this still really an issue? in my deployments on one cluster only cephadm shell works out of the box without providing any additional parameters
Updated by Redouane Kachach Elhichou about 2 years ago
- Assignee set to Redouane Kachach Elhichou
Updated by Redouane Kachach Elhichou about 2 years ago
- Status changed from New to In Progress
Updated by Redouane Kachach Elhichou about 2 years ago
- Status changed from In Progress to Fix Under Review
Updated by Redouane Kachach Elhichou about 2 years ago
Issue being addressed by the PR: https://github.com/ceph/ceph/pull/45070
Updated by Redouane Kachach Elhichou about 2 years ago
- Pull request ID set to 45070
Updated by Redouane Kachach Elhichou about 2 years ago
- Status changed from Fix Under Review to Resolved
Actions