Bug 1798153

Summary: Dashboard does not allow you to set norebalance OSD flag
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: John Brier <jbrier>
Component: Ceph-DashboardAssignee: Nizamudeen <nia>
Status: CLOSED ERRATA QA Contact: Sunil Angadi <sangadi>
Severity: medium Docs Contact: Anjana Suparna Sriram <asriram>
Priority: medium    
Version: 4.0CC: ceph-eng-bugs, ceph-qe-bugs, epuertat, hyelloji, nia, sangadi, tserlin
Target Milestone: rcKeywords: UserExperience
Target Release: 4.1Flags: hyelloji: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ceph-14.2.8-9.el8, ceph-14.2.8-7.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-19 17:32:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of available cluster-wide OSD flags showing no rebalance option none

Description John Brier 2020-02-04 17:01:58 UTC 
Created attachment 1657629 [details]
screenshot of available cluster-wide OSD flags showing no rebalance option

Description of problem:

In the Admin Guide, in order to shutdown or reboot the OSD nodes, we instruct the customer to set cluster-wide OSD flags noout, norecover, norebalance, nobackfill, nodown  [1] However, in the dashboard under > Cluster > OSDs > Cluster-wide Flags, you can set all of those flags except norebalance.


Version-Release number of selected component (if applicable):

[root@jb-ceph4-mon ~]# rpm -qa | grep dashboard
ceph-grafana-dashboards-14.2.4-125.el8cp.noarch
ceph-mgr-dashboard-14.2.4-125.el8cp.noarch

1) https://access.redhat.com/documentation/en-us/red_hat_ceph_storage/4/html-single/administration_guide/index#powering-down-and-rebooting-a-red-hat-ceph-storage-cluster_admin
Comment 9 errata-xmlrpc 2020-05-19 17:32:09 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2020:2231