Bug 1421975 - HA VM is not started when it's host goes down and it was started through run once
Summary: HA VM is not started when it's host goes down and it was started through run ...
Keywords:
Status: CLOSED DUPLICATE of bug 1341106
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Virt
Version: 4.1.1
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Michal Skrivanek
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-02-14 09:11 UTC by Petr Matyáš
Modified: 2017-02-15 10:08 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2017-02-15 10:08:39 UTC
oVirt Team: Virt
Embargoed:


Attachments (Terms of Use)

Description Petr Matyáš 2017-02-14 09:11:27 UTC
Description of problem:
I started a HA VM (migratable but with preferred host) through run once and set the preferred host as the one VM should run on. After that when the host gets fenced or goes down with whatever reason, the HA VM is not restarted on another host.

Version-Release number of selected component (if applicable):
4.1.1-1

How reproducible:
always

Steps to Reproduce:
1. edit a VM, set it as highly available and set preferred host and auto migration when necessary policy
2. run the VM with run once and set preferred host as the one VM should run on
3. fence the preferred host

Actual results:
HA VM is not restarted

Expected results:
HA VM should be started on another host

Additional info:

Comment 5 Michal Skrivanek 2017-02-15 10:08:39 UTC
the issue is addressed by bug 1341106

*** This bug has been marked as a duplicate of bug 1341106 ***


Note You need to log in before you can comment on or make changes to this bug.