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

Bug 1077706

Summary:

HA vms not starts on host with PM that restarted via engine

Product:

Red Hat Enterprise Virtualization Manager

Reporter:

Artyom <alukiano>

Component:

ovirt-engine

Assignee:

Arik <ahadas>

Status:

CLOSED CURRENTRELEASE

QA Contact:

Artyom <alukiano>

Severity:

urgent

Docs Contact:

Priority:

unspecified

Version:

3.4.0

CC:

acathrow, ahadas, alukiano, cpelland, gchaplik, gklein, iheim, lpeer, mavital, michal.skrivanek, ofrenkel, Rhev-m-bugs, sherold, yeylon

Target Milestone:

---

Target Release:

3.4.0

Hardware:

Unspecified

OS:

Unspecified

Whiteboard:

virt

Fixed In Version:

org.ovirt.engine-root-3.4.0-14

Doc Type:

Bug Fix

Doc Text:

Story Points:

---

Clone Of:

Environment:

Last Closed:

2014-06-12 14:05:25 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:

Attachments:

Description	Flags
engine log	none

Description Artyom 2014-03-18 13:02:28 UTC

Description of problem:
I have two hosts, host_1 in maintenance(for fencing operation) and host_2 with PM, on host_2 I run 4 HA vms. If host_2 failed(crash, power outage) and after it power on automatic via PM, HA vms not started automatically on it.

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

How reproducible:
Always

Steps to Reproduce:
1. Add two host_1(in maintenance) and host_2 in state up with PM
2. Add 4 HA vms and start them on host_2
3. Run poweroff -f command on host_2(via ssh for example)
4. Wait until host_2 return to state up

Actual results:
HA vms not started automatically on host_2

Expected results:
HA vms started automatically on host_2

Additional info:

Comment 1 Omer Frenkel 2014-03-19 08:02:29 UTC

please attach engine log

Comment 2 Gilad Chaplik 2014-03-20 15:39:24 UTC

Arik, can you please fill in the doc text section, thanks!

Comment 3 Gilad Chaplik 2014-03-20 15:41:18 UTC

(In reply to Gilad Chaplik from comment #2)
> Arik, can you please fill in the doc text section, thanks!

same for bug 1078553

Comment 4 Arik 2014-03-23 16:27:17 UTC

Created attachment 877873 [details]
engine log

Comment 5 Michal Skrivanek 2014-04-01 13:04:21 UTC

stuff merged to master, backport ongoing

Comment 6 Arik 2014-04-03 08:37:35 UTC

http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=f62e9a72cf533d307db8c4343948d45ed784856d
http://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=commit;h=311cd34a860b5e432ea790e18d08cc29bd6d4be0

Comment 7 Artyom 2014-04-27 07:46:27 UTC

I check patch on av7, and I see that now engine try to start HA vms number of times until it success or it come to limit of attempts.
It also a good idea to add new parameters to engine-config:
1) Number of attempts to start vms
2) Time between attempts(in seconds)

Because each host have different boot time.

Comment 8 Arik 2014-04-27 13:39:44 UTC

(In reply to Artyom from comment #7)
> It also a good idea to add new parameters to engine-config:
> 1) Number of attempts to start vms
> 2) Time between attempts(in seconds)
> 
> Because each host have different boot time.

Right, I don't think it should be coupled to this bug though, it is more a RFE for enhancing the mechanism that was recently introduced for restarting HA VMs. I posted a patch for that: http://gerrit.ovirt.org/27114

Comment 9 Artyom 2014-04-28 08:45:31 UTC

Verified on av7

Comment 10 Itamar Heim 2014-06-12 14:05:25 UTC

Closing as part of 3.4.0