Verified with rhevm-3.6.9-0.1.el6.noarch.
Had a cluster with 126 Vms running.
Changed cluster compatibility version from 3.5 to 3.6 (hosts were 3.6 all the time) and monitored the updateVm calls with tail on engine log.
Repeated this several times (each time setting the cluster compatibility back to 3.5 via DB.
Ran the upgrade for 5 times, no race has occurred.
Please advise if this test isn't sufficient.
I see this test was approved in the 4.0.4 version of it. 10x.
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.
I have a customer running 3.6.9 that just hit this in a cluster that only has 30 VMs. I am gathering all the data and will open a new BZ.
This is happening on every attempt to upgrade the cluster. I will grab the engine log and post the related errors into this BZ.
(In reply to Frank DeLorey from comment #8)
> This is happening on every attempt to upgrade the cluster. I will grab the
> engine log and post the related errors into this BZ.
It is a different issue, tracked in bug 1389764 now