Bugzilla (bugzilla.redhat.com) will be under maintenance for infrastructure upgrades and will not be unavailable on July 31st between 12:30 AM - 05:30 AM UTC. We appreciate your understanding and patience. You can follow status.redhat.com for details.
Bug 1343652 - Disk removal does not change status of the OSD host
Summary: Disk removal does not change status of the OSD host
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Storage Console
Classification: Red Hat
Component: unclassified
Version: 2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: 2
Assignee: Nishanth Thomas
QA Contact: sds-qe-bugs
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-06-07 15:12 UTC by Lubos Trilety
Modified: 2016-06-17 11:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-06-17 11:48:02 UTC
Target Upstream Version:


Attachments (Terms of Use)
host status (47.68 KB, image/png)
2016-06-07 15:12 UTC, Lubos Trilety
no flags Details

Description Lubos Trilety 2016-06-07 15:12:15 UTC
Created attachment 1165686 [details]
host status

Description of problem:
Disk removal from OSD machine generate a warning event, however status of the machine is not changed to warning.

Version-Release number of selected component (if applicable):
rhscon-core-0.0.21-1.el7scon.x86_64
rhscon-ceph-0.0.20-1.el7scon.x86_64
rhscon-ui-0.0.34-1.el7scon.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create some cluster
2. Remove a disk from OSD host, wait until the event is created
3. List a host

Actual results:
Status of the host was not changed it is still in OK state

Expected results:
Host should have Warn state at least until the event is not dismissed.

Additional info:

Comment 1 Darshan 2016-06-17 11:48:02 UTC
This is expected behavior. When a disk that is consumed by an osd is removed. An event will be shown saying the disk was removed. Another alert indicating the osd is down will be shown. And the alarm count of the host is incremented by 1. We wont change the state of the host.


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