Bug 1166083 - [RHSC] - Reinstalling of host does not change the status to up.
Summary: [RHSC] - Reinstalling of host does not change the status to up.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Gluster Storage
Classification: Red Hat Storage
Component: rhsc
Version: rhgs-3.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: RHGS 3.0.3
Assignee: Ramesh N
QA Contact: RamaKasturi
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-11-20 11:50 UTC by RamaKasturi
Modified: 2015-05-13 17:42 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-15 13:50:12 UTC
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0039 0 normal SHIPPED_LIVE Red Hat Storage Console 3.0 enhancement and bug fix update #3 2015-01-15 18:46:40 UTC

Description RamaKasturi 2014-11-20 11:50:01 UTC
Description of problem:
When a host is moved to maintenance and user tries to reinstall the host, once the installtion process gets completed, the host status still remains in 'Maintenanace' mode and does not come back 'UP'

Version-Release number of selected component (if applicable):
rhsc-3.0.3-1.19.el6rhs.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install RHSC.
2. Add a host to console.
3. Move it to maintenance.
4. Click on re-install link in the hosts tab.

Actual results:
Host status remains in Maintenanace and engine does not mark it 'UP'

Expected results:
Host status should be marked UP

Additional info:

Comment 2 RamaKasturi 2014-11-27 12:33:42 UTC
Verified and works fine with build rhsc-3.0.3-1.20.el6rhs.noarch.

When the host is put in maintenance and re-installing the host brings back the host to UP state.

Comment 4 errata-xmlrpc 2015-01-15 13:50:12 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://rhn.redhat.com/errata/RHBA-2015-0039.html


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