Description of problem:
After a network outage some VMs are started on more then one hypervisor
as they are incorrectly considered as in down state.
Version-Release number of selected component (if applicable):
Not clear yet
Steps to Reproduce:
Not clear yet, but the scenario could be:
1. intall more then on hypervisor
2. prevent RHEV-M to connecto to those VMs (also power management
is defunct due to netwrok outage)
3. Let one hyoervisor to be reachable by RHEV-M
Some VMs are considered as down and are started on another hypervisor
Vms are marked as in unknown stated
Roman - can you get the logs from the host bl460-282 with data time after the one attached - i.e 2014-02-15 15:01:01 and onward
I want to see what this host reported to backend as its internal vm list
and this might explain this.
If the host reported that vm svcz0plgfa50 is not in its list currently,
then its only natural to see this
2014-02-15 15:09:59,229 INFO [org.ovirt.engine.core.bll.VdsEventListener] (DefaultQuartzScheduler_Worker-61) [5989b7e9] Highly Available VM went down. Attempting to restart. VM Name: svcz0plgfa50-bwd00, VM Id:1
Roy, I'm all for option 1
Verified on av3
Until host on what runs vms, not change status to up, vms stay in unknown status
*** Bug 1090536 has been marked as a duplicate of this bug. ***
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.