Bug 1351953 - Console doesn't detect if device is removable
Summary: Console doesn't detect if device is removable
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat Storage
Component: core
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 3
Assignee: Nishanth Thomas
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-01 09:00 UTC by Martin Kudlej
Modified: 2017-03-23 04:04 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-03-23 04:04:54 UTC
Embargoed:


Attachments (Terms of Use)

Description Martin Kudlej 2016-07-01 09:00:01 UTC
Description of problem:
I've tried to add removable usb device to machine before accepting node and Console has add this device to "Raw capacity". Finally it hasn't use it for OSD. But I expect that Console should not use removable disk for counting "Raw capacity" in Cluster wizard at page "Select Hosts". Removable disks should be ignored.

Version-Release number of selected component (if applicable):
server:
ceph-ansible-1.0.5-23.el7scon.noarch
ceph-installer-1.0.12-3.el7scon.noarch
rhscon-ceph-0.0.27-1.el7scon.x86_64
rhscon-core-0.0.28-1.el7scon.x86_64
rhscon-core-selinux-0.0.28-1.el7scon.noarch
rhscon-ui-0.0.42-1.el7scon.noarch

storage node:
ceph-base-10.2.2-5.el7cp.x86_64
ceph-common-10.2.2-5.el7cp.x86_64
ceph-osd-10.2.2-5.el7cp.x86_64
ceph-selinux-10.2.2-5.el7cp.x86_64
libcephfs1-10.2.2-5.el7cp.x86_64
python-cephfs-10.2.2-5.el7cp.x86_64
rhscon-agent-0.0.13-1.el7scon.noarch


How reproducible:
100%

Steps to Reproduce:
1. add USB *Removable* device to one machine before accepting of nodes
2. accept nodes
3. try to create cluster and check "Raw Capacity" if there is also counted this drive

Actual results:
Removable device is counted to "Raw Capacity".

Expected results:
Removable device should be completely ignored in Console.


Note You need to log in before you can comment on or make changes to this bug.