Bug 1623580

Summary: [RFE] Prevent customers from installing an OSD device on the same disk as the OS
Product: [Red Hat Storage] Red Hat Ceph Storage Reporter: Neil Levine <nlevine>
Component: Ceph-AnsibleAssignee: Guillaume Abrioux <gabrioux>
Status: CLOSED ERRATA QA Contact: Sunil Kumar Nagaraju <sunnagar>
Severity: low Docs Contact: Bara Ancincova <bancinco>
Priority: low    
Version: 3.2CC: aschoen, ceph-eng-bugs, ceph-qe-bugs, gabrioux, gmeno, nthomas, pasik, sunnagar, tserlin, vashastr
Target Milestone: z3Keywords: FutureFeature
Target Release: 3.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: RHEL: ceph-ansible-3.2.32-1.el7cp Ubuntu: ceph-ansible_3.2.32-2redhat1 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-12-19 17:58:55 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 Neil Levine 2018-08-29 16:38:48 UTC
As an admin, I cannot install an OSD on the same physical device as my operating system as this will cause performance issues.

Comment 3 Sébastien Han 2018-09-05 12:08:11 UTC
With the introduction of choose_disk we won't have to specify devices anymore by there system name (e,g: /dev/sda) so this will get solved naturally.

Comment 4 Giridhar Ramaraju 2019-08-05 13:09:00 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:10:22 UTC
Updating the QA Contact to a Hemant. Hemant will be rerouting them to the appropriate QE Associate. 

Regards,
Giri

Comment 6 Giridhar Ramaraju 2019-08-20 07:13:09 UTC
evel setting the severity of this defect to "High" with a bulk update. Pls
refine it to a more closure value, as defined by the severity definition in
https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity

Comment 18 errata-xmlrpc 2019-12-19 17:58:55 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-2019:4353