Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1421975

Summary: HA VM is not started when it's host goes down and it was started through run once
Product: [oVirt] ovirt-engine Reporter: Petr Matyáš <pmatyas>
Component: BLL.VirtAssignee: Michal Skrivanek <michal.skrivanek>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.1.1CC: bugs, pmatyas
Target Milestone: ---Keywords: AutomationBlocker
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-02-15 10:08:39 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

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 ***