Red Hat Bugzilla – Bug 1026344
Disconnect storage pool in case of unsuccessful hosted-engine setup.
Last modified: 2014-01-21 11:55:03 EST
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.
As workaround you can just reboot or use a script like this:
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
I've encountered the same issue (after a failed run due to wrong cpu type).
Patch merged on upstream master and 1.0 branches
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.