Bug 1106556 - Engine vm is not killed after that deployment process aborted
Summary: Engine vm is not killed after that deployment process aborted
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-hosted-engine-setup
Version: 3.4.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
: 3.5.0
Assignee: Yedidyah Bar David
QA Contact: Artyom
URL:
Whiteboard: integration
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-06-09 15:04 UTC by Artyom
Modified: 2015-02-11 20:40 UTC (History)
9 users (show)

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.
Clone Of:
Environment:
Last Closed: 2015-02-11 20:40:11 UTC
oVirt Team: ---
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:0161 0 normal SHIPPED_LIVE ovirt-hosted-engine-setup bug fix and enhancement update 2015-12-07 21:35:11 UTC
oVirt gerrit 35449 0 master MERGED packaging: setup: Allow destroying VM when aborting Never
oVirt gerrit 35460 0 ovirt-hosted-engine-setup-1.2 MERGED packaging: setup: Allow destroying VM when aborting Never

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
Note You need to log in before you can comment on or make changes to this bug.