Bug 1066373

Summary: When re-running --deploy, ha services should be stopped to allow re-using existing storage
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: ovirt-hosted-engine-setupAssignee: Sandro Bonazzola <sbonazzo>
Status: CLOSED ERRATA QA Contact: Jiri Belka <jbelka>
Severity: high Docs Contact:
Priority: high    
Version: 3.3.0CC: aburden, adingman, dfediuck, didi, gpadgett, iheim, jbelka, movciari, mpavlik, oschreib, pstehlik, sbonazzo, scohen, ukar, zdover
Target Milestone: ---Keywords: Triaged, ZStream
Target Release: 3.3.2   
Hardware: x86_64   
OS: Linux   
Whiteboard: integration
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Previously, the high availability daemon was enabled by the rpm install and not stopped upon termination of a hosted-engine deployment. This meant that if the hosted engine was deployed, but was aborted or failed after having created the engine virtual machine, the hosted engine could not be redeployed as it conflicted with the virtual machine already started by the high availability daemon. Now, the high availability daemon is enabled by hosted-engine deployment, and the hosted engine checks for an existing virtual machine running on the host. Redeployment of the hosted engine no longer fails due to the presence of a virtual machine created during a previous deployment.
Story Points: ---
Clone Of: 1034726 Environment:
Last Closed: 2014-04-09 17:42:31 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1034726    
Bug Blocks:    

Comment 1 Sandro Bonazzola 2014-03-04 12:41:52 UTC
Merged upstream on 1.0 branch on -setup side, pending merge on -ha side

Comment 2 Greg Padgett 2014-03-04 13:55:12 UTC
Merged on -ha side, change-id I9064a8a7bc28d0e581f2311d11b9fdca375dd3b5

Comment 5 errata-xmlrpc 2014-04-09 17:42:31 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-0390.html