Bug #43016
mgr/dashboard: 'always on' modules should be indicated as 'enabled' in dashboard (even if they can't be disabled)
Status:
Duplicate
Priority:
Normal
Assignee:
Category:
General - Configuration
Target version:
% Done:
0%
Source:
Q/A
Tags:
Backport:
Regression:
No
Severity:
3 - minor
Reviewed:
Affected Versions:
ceph-qa-suite:
Pull request ID:
Crash signature (v1):
Crash signature (v2):
Description
While IMHO the issue should lie within mgr boundaries, given the reasons stated in https://github.com/ceph/ceph/commit/44b50af998d059eb409dd95c60a59d279c1c9020, it might make sense to keep "always_on" modules treated as a special case.
Hence, I'd suggest to display them as enabled but not modifiable (grayed out). In fact, initially dashboard allowed users to disable/enable always-on modules, but that was later modified: https://github.com/ceph/ceph/pull/30142.
Related issues
History
#1 Updated by Ernesto Puerta about 4 years ago
- Duplicates Bug #41648: mgr/dashboard: Add support for "always_on_modules" added
#2 Updated by Lenz Grimmer almost 4 years ago
- Assignee set to Volker Theile
#3 Updated by Volker Theile almost 4 years ago
- Status changed from New to Duplicate
#4 Updated by Volker Theile almost 4 years ago
- Duplicates Backport #42809: nautilus: mgr/dashboard: Add support for "always_on_modules" added
#5 Updated by Nathan Cutler almost 4 years ago
- Backport deleted (
nautilus)
Backport will be handled via #41648
#6 Updated by Ernesto Puerta over 2 years ago
- Project changed from mgr to Dashboard
- Category changed from 158 to General - Configuration