Bug 911696

Summary: [Sync configuration with glusterFS] Peer probe results in Console Install Failure
Product: [Red Hat Storage] Red Hat Gluster Storage Reporter: Matt Mahoney <mmahoney>
Component: rhscAssignee: Alon Bar-Lev <alonbl>
Status: CLOSED NOTABUG QA Contact: Prasanth <pprakash>
Severity: medium Docs Contact:
Priority: medium    
Version: 2.1CC: alonbl, avishwan, barumuga, iheim, rhs-bugs, shaines, shireesh
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-03-19 18:42:20 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
Console engine log none

Description Matt Mahoney 2013-02-15 16:54:06 UTC
Created attachment 697877 [details]
Console engine log

Description of problem:
After doing a peer probe, the Console reported an install failure. This occurs when doing two or more rounds of peer probe and peer detach iterations. Peer status lists that the newly added server is available, while the console reports the install failure.

Version-Release number of selected component (if applicable):
QA5

How reproducible:


Steps to Reproduce:
1. From server-a, peer probe server-b
2. From console, import server-b (via cluster.general)
3. If server has added successfully; from server-a, peer detach server-b
  - Repeat steps 1-3 until failure occurs.
  
Actual results:


Expected results:
Server should be added and removed via Gluster command line without causing console install error.

Additional info:

Comment 2 Shireesh 2013-02-18 09:43:59 UTC
Following seems like the relevant error from the engine log:

2013-02-14 20:59:42,835 ERROR [org.ovirt.engine.core.utils.ssh.SSHDialog] (pool-3-thread-47) SSH error running command root.122.131:'umask 0077; MYTMP="$(mktemp -t ovirt-XXXXXXXXXX)"; trap "chmod -R u+rwX \"${MYTMP}\" > /dev/null 2>&1; rm -fr \"${MYTMP}\" > /dev/null 2>&1" 0; rm -fr "${MYTMP}" && mkdir "${MYTMP}" && python -c "import sys, tarfile; tarfile.open(fileobj=sys.stdin, mode='r|').extractall(path='${MYTMP}')" &&  "${MYTMP}"/setup DIALOG/dialect=str:machine DIALOG/customization=bool:True': java.io.IOException: Command returned failure code 1 during SSH session 'root.122.131'
	at org.ovirt.engine.core.utils.ssh.SSHClient.executeCommand(SSHClient.java:506) [engine-utils.jar:]
	at org.ovirt.engine.core.utils.ssh.SSHDialog.executeCommand(SSHDialog.java:308) [engine-utils.jar:]
	at org.ovirt.engine.core.bll.VdsDeploy.execute(VdsDeploy.java:902) [engine-bll.jar:]
	at org.ovirt.engine.core.bll.InstallVdsCommand.executeCommand(InstallVdsCommand.java:162) [engine-bll.jar:]

Alon, can you please help here?

Comment 3 Alon Bar-Lev 2013-02-18 16:58:29 UTC
Please attach:
/var/log/ovirt-engine/host-deploy/ovirt-20130214205942-192.168.122.131.log

Comment 4 Scott Haines 2013-02-26 22:51:56 UTC
Per Feb 20 bug triage meeting, targeting for 2.1.

Comment 5 Shireesh 2013-03-01 07:16:56 UTC
Matt, please provide the log requested by Alon.

Comment 6 Matt Mahoney 2013-03-19 18:42:20 UTC
Not reproducible in QA8. Will re-open if encountered again.