Bug 963676

Summary: [RHSC] Add host failure (RHS Anshi node to rhsc-2.0.techpreview1-4.el6rhs.noarch)
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Shruti Sampat <ssampat>
Component: rhscAssignee: Timothy Asir <tjeyasin>
Status: CLOSED ERRATA QA Contact: Shruti Sampat <ssampat>
Severity: high Docs Contact:
Priority: high    
Version: 2.0CC: dtsang, fharshav, knarra, mmahoney, pprakash, rhs-bugs, sabose, sdharane
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: vdsm-4.9.6-23.el6rhs.x86_64 Doc Type: Bug Fix
Doc Text:
Cause: There was an error in Gluster Package Bootstrap component of vdsm Consequence: When trying to add Anshi node to RHSC Tech Preview Console, there is an installation failure while trying to install vdsm-gluster package. Fix: Corrected the vdsm bootstrap component for gluster Result: Able to successfully add Anshi node to RHSC Tech Preview console.
 Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-15 21:52:29 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
vdsm logs
none
engine logs none

Description Shruti Sampat 2013-05-16 11:18:33 UTC 
Created attachment 748757 [details]
engine logs

Description of problem:
------------------------------------------------------------------------------
Trying to add a glusterfs Anshi (glusterfs-3.3.0.7rhs-1.el6rhs.x86_64) to rhsc-2.0.techpreview1-4.el6rhs.noarch fails with the following errors in the engine logs - 

2013-05-16 00:39:33,647 INFO  [org.ovirt.engine.core.bll.VdsInstaller] (pool-6-thread-50) [7f436fa2] Installation of 10.14.16.193. Recieved message: <
BSTRAP component='VDS PACKAGES' status='OK' result='sanlock' message='sanlock-2.3-4.el6_3.x86_64 '/>
<BSTRAP component='VDS PACKAGES' status='OK' result='sanlock-python' message='sanlock-python-2.3-4.el6_3.x86_64 '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='v' message='package v is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='d' message='package d is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='s' message='package s is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='m' message='package m is not installed '/>
. FYI. (Stage: Running first installation script on Host)
2013-05-16 00:39:34,766 ERROR [org.ovirt.engine.core.bll.VdsInstaller] (pool-6-thread-50) [7f436fa2] Installation of 10.14.16.193. Recieved message: <
BSTRAP component='GLUSTER PACKAGES' status='WARN' result='-' message='package - is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='g' message='package g is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='l' message='package l is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='u' message='package u is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='s' message='package s is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='t' message='package t is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='e' message='package e is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='WARN' result='r' message='package r is not installed '/>
<BSTRAP component='GLUSTER PACKAGES' status='FAIL' result='r' message='Loaded plugins: aliases, changelog, downloadonly, fastestmirror, filter-data,               : keys, list-data, merge-conf, priorities, product-id,               : protectbase, rhnplugin, security, subscription-manager, tmprepo,               : tsflags, upgrade-helper, verify, versionlock Updating certificate-based repositories. Loading mirror speeds from cached hostfile Skipping filters plugin, no data 0 packages excluded due to repository protections Setting up Install Process No package r available. Error: Nothing to do '/>

Version-Release number of selected component (if applicable):
rhsc-2.0.techpreview1-4.el6rhs.noarch

glusterfs-3.3.0.7rhs-1.el6rhs.x86_64

vdsm-4.9.6-20.el6rhs.x86_64

How reproducible:
Frequently

Steps to Reproduce:
1. Setup a storage node with RHS Anshi.
2. Perform the workaround described in bug 875795
3. Add the host to a cluster via the Console.
  
Actual results:
Host ends up in 'Install Failed' state with the above described error in the engine logs.

Expected results:
Host should get installed successfully.

Additional info:
Comment 1 Shruti Sampat 2013-05-16 11:19:09 UTC 
Created attachment 748758 [details]
vdsm logs
Comment 3 Sahina Bose 2013-05-16 12:18:09 UTC 
Please confirm if workarounds mentioned in bugs 924193 and 928311 have been applied before adding host
Comment 4 Shruti Sampat 2013-05-16 13:44:37 UTC 
Step 2 in 'Steps to Reproduce' should read as -

2. Perform the workaround described in bug 924193
Comment 5 Shruti Sampat 2013-05-16 13:52:37 UTC 
Hi Sahina,

Tried the workarounds mentioned in both bug 924193 and bug 924193. I am still facing the same issue. Reattaching engine logs.

Thanks,
Shruti
Comment 6 Shruti Sampat 2013-05-16 13:55:04 UTC 
Created attachment 748869 [details]
engine logs
Comment 8 Timothy Asir 2013-05-25 12:20:31 UTC 
This bug will appear only when the engine bootstraps the node.
I have fixed the error in VDSM bootstrap.

Before installing the vdsm bootstrap rpm, it is necessary to stop the engine;
then after it can be installed (vdsm bootstrap rpm) in the engine and start.
Comment 9 Shruti Sampat 2013-05-27 11:29:32 UTC 
Performed the following steps -

1. Stop jbossas service on the machine.
2. Update the vdsm-bootstrap package to vdsm-bootstrap-4.9.6-23.el6rhs.noarch.
3. Start jbossas service.
4. Add the storage node now.

The node comes up.

Marking the bug as verified.
Comment 10 Sahina Bose 2013-05-28 10:39:58 UTC 
*** Bug 956396 has been marked as a duplicate of this bug. ***
Comment 12 errata-xmlrpc 2013-07-15 21:52:29 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.

http://rhn.redhat.com/errata/RHBA-2013-1064.html