Bug 1026344

Summary:	Disconnect storage pool in case of unsuccessful hosted-engine setup.
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Leonid Natapov <lnatapov>
Component:	ovirt-hosted-engine-setup	Assignee:	Sandro Bonazzola <sbonazzo>
Status:	CLOSED ERRATA	QA Contact:	movciari
Severity:	medium	Docs Contact:
Priority:	high
Version:	unspecified	CC:	dfediuck, iheim, oschreib, pablo.iranzo, pstehlik, scohen
Target Milestone:	---	Keywords:	Triaged
Target Release:	3.3.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	integration
Fixed In Version:	ovirt-hosted-engine-setup-1.0.0-0.10.1.rc.el6ev	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-01-21 16:55:03 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:

Description Leonid Natapov 2013-11-04 13:34:32 UTC

If hosted engine setup was for some reason unsuccessful we still have storage pool connected as a leftover of previous setup. 
If user tries to run setup again he will get an error:

 [ ERROR ] The following storage pool has been found connected: dff9559f-3587-41fd-8af2-5d71fc902f5c
[ ERROR ] Failed to execute stage 'Environment customization': Cannot setup Hosted Engine with connected storage pools

We should disconnect storage pool that we created in case of  unsuccessful setup.

Comment 1 Sandro Bonazzola 2013-11-05 15:27:09 UTC

As workaround you can just reboot or use a script like this:

 #!/bin/sh
 spUUID=`vdsClient -s localhost getConnectedStoragePoolsList`
 sdUUID=`vdsClient -s localhost getStorageDomainsList $spUUID`
 vdsClient -s localhost spmStop $spUUID
 vdsClient -s localhost disconnectStoragePool $spUUID 1 $sdUUID

where 1 is the host id for first host.
Postponing to 3.3.1

Comment 2 Ofer Schreiber 2013-11-26 13:20:24 UTC

I've encountered the same issue (after a failed run due to wrong cpu type).

Comment 3 Sandro Bonazzola 2013-12-02 13:43:50 UTC

Patch merged on upstream master and 1.0 branches

Comment 5 errata-xmlrpc 2014-01-21 16:55:03 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-2014-0083.html