Bug 919422

Summary: [RHSC] Host after being rebooted, goes to non-responsive state momentarily before coming UP
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhscAssignee: Sahina Bose <sabose>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: medium Docs Contact:
Priority: low    
Version: 2.1CC: dpati, dtsang, knarra, mmahoney, pprakash, rhs-bugs, rhsc-qe-bugs, rnachimu, sabose, sdharane
Target Milestone: ---Keywords: ZStream
Target Release: RHGS 3.0.3   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: rhsc-3.0.2-1.16.el6rhs.noarch.rpm Doc Type: Bug Fix
Doc Text:
Cause: Rebooting of host causes vdsm to restart Consequence: Host state changes to Non-responsive while vdsm is restarting Fix: State changes of host were fixed to Initializin state when the host is booting up and vdsm is restarting Result: Host no longer goes to Non-responsive state
 Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-15 13:47:19 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:
Attachments:
Description Flags
engine logs
none
new engine logs none

Description Shruti Sampat 2013-03-08 12:24:33 UTC 
Description of problem:
---------------------------------------
After adding a host to a cluster via the UI, it goes to non-responsive mode for a moment before coming UP.

Version-Release number of selected component (if applicable):
Red Hat Storage Console Version: 2.1.0-0.qa7.el6rhs 

How reproducible:
Intermittent

Steps to Reproduce:
1. Add a host to a cluster via the Console.
  
Actual results:
Host after reboot, goes to non-responsive state before coming UP.

Expected results:
Host should come UP after a reboot and not go to non-responsive state.

Additional info:
Comment 2 Sahina Bose 2013-03-11 09:57:25 UTC 
Could you provide engine log?
Comment 3 Shruti Sampat 2013-03-11 10:18:44 UTC 
Created attachment 708295 [details]
engine logs
Comment 4 Shireesh 2013-03-11 12:13:20 UTC 
What is the name/ip of the server you were trying to add?

Also, I think the engine.log provided by you won't help, as it contains only those events that happened on 11th March, whereas you have faced the issue on 8th March. The log file probably got rotated - can you check and attach the right one?
Comment 5 Shruti Sampat 2013-03-14 07:17:27 UTC 
Created attachment 709885 [details]
new engine logs
Comment 6 Shruti Sampat 2013-03-14 09:29:17 UTC 
I saw this issue in another setup today, so attached the engine logs. The server I was trying to add in this case was 10.70.35.161.
Comment 7 Shruti Sampat 2013-07-04 12:30:50 UTC 
Sahina,

This issue of the server being Non-responsive momentarily after bootstrap seems to have been fixed. I have not seen it for a while now. The server now is in the 'Initializing' state for a while before coming UP.
Comment 11 Shruti Sampat 2014-11-19 10:50:50 UTC 
Verified as fixed in rhsc-3.0.3-1.17.el6rhs.noarch.
Comment 13 errata-xmlrpc 2015-01-15 13:47:19 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