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-setup | Assignee: | Yedidyah Bar David <didi> |
Status: | CLOSED ERRATA | QA Contact: | Artyom <alukiano> |
Severity: | high | Docs Contact: | |
Priority: | unspecified | ||
Version: | 3.4.0 | CC: | 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
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. 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. 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. 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 |