Bug 1581421

Summary: [RFE] If the nodeep-scrub/noscrub flags are set in pools instead of global cluster. List the pool names in the ceph status
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Vikhyat Umrao <vumrao>
Component: RADOSAssignee: Neha Ojha <nojha>
Status: CLOSED ERRATA QA Contact: Manohar Murthy <mmurthy>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.5CC: ceph-eng-bugs, ceph-qe-bugs, dzafman, hyelloji, kchai, kdreyer, mhackett, nojha, tserlin
Target Milestone: rcKeywords: FutureFeature
Target Release: 4.1Flags: hyelloji: needinfo-
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: ceph-14.2.8-3.el8, ceph-14.2.8-3.el7 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-05-19 17:30:39 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:

Description Vikhyat Umrao 2018-05-22 17:48:34 UTC 
Description of problem:
[RFE] If the nodeep-scrub/noscrub flags are set in pools instead of global cluster list in the ceph status the pool name

Version-Release number of selected component (if applicable):
RHCS 2.y
RHCS 3.0
Comment 2 Vikhyat Umrao 2019-05-07 17:40:06 UTC 
Merged in master - https://github.com/ceph/ceph/pull/26488 I have changed backport to nautilus http://tracker.ceph.com/issues/38029 so it can become part of 4.0.
Comment 4 Giridhar Ramaraju 2019-08-05 13:06:28 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 5 Giridhar Ramaraju 2019-08-05 13:09:07 UTC 
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri
Comment 11 errata-xmlrpc 2020-05-19 17:30:39 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