Bug 1106556

Summary: Engine vm is not killed after that deployment process aborted
Product: Red Hat Enterprise Virtualization Manager Reporter: Artyom <alukiano>
Component: ovirt-hosted-engine-setupAssignee: Yedidyah Bar David <didi>
Status: CLOSED ERRATA QA Contact: Artyom <alukiano>
Severity: high Docs Contact:
Priority: unspecified    
Version: 3.4.0CC: aberezin, aburden, dfediuck, didi, gklein, iheim, michal.skrivanek, sbonazzo, sherold
Target Milestone: ---Keywords: Triaged
Target Release: 3.5.0   
Hardware: x86_64   
OS: Linux   
Whiteboard: integration
Fixed In Version: ovirt-hosted-engine-setup-1.2.1-5.el7ev Doc Type: Bug Fix
Doc Text:
Previously, if the deployment of the hosted engine was aborted after the engine virtual machine had been created, a subsequent deployment would fail until the engine virtual machine had been manually destroyed. Now, an option has been added so that the engine virtual machine is destroyed when the deployment is aborted.
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-02-11 20:40:11 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:

Description Artyom 2014-06-09 15:04:30 UTC
Description of problem:
Engine vm is not killed after that deployment process aborted, if coming to stage where you need to install OS, and choose 3(Abort setup) option, vm will stay exist and you will need to kill it manually.

Version-Release number of selected component (if applicable):
ovirt-hosted-engine-setup-1.1.2-5.el6ev.noarch

How reproducible:
Always

Steps to Reproduce:
1. Run hosted-engine --deploy
2. Abort setup on OS installation stage
3.

Actual results:
Engine vm still exist after abort 

Expected results:
vm killed automatically in case of abort

Additional info:

Comment 3 Doron Fediuck 2014-10-01 08:34:12 UTC
This will be handled by adding an option.
So the user can choose to abort setup and keep the VM alive, or
abort setup and kill the VM.

Comment 4 Yedidyah Bar David 2014-11-19 08:43:05 UTC
Clarification: There are two dialogs that allow aborting, one after the os is supposed to be installed and another after engine is supposed to be setup. I'll add a fourth option 'Abort and destroy VM' to both of them.

Comment 6 Artyom 2014-12-23 14:23:31 UTC
Verified on ovirt-hosted-engine-setup-1.2.1-8.el7ev.noarch
On two stages after OS and engine installation in both cases, vm destroyed if I choose 4 option.

Comment 8 errata-xmlrpc 2015-02-11 20:40:11 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.

https://rhn.redhat.com/errata/RHBA-2015-0161.html