Red Hat Bugzilla – Bug 1016118
async between masterVersion : can't connect to StoragePool
Last modified: 2016-02-10 12:05:50 EST
Description of problem:
We had a power outage while using ovirt 3.3.
it seems like the masterVersion was repeatedly updated in the database and was not updated in the storage hence the engine is failing to connect to the master storage domain
currently the behaviour is that the current master can't be selected as new master, that's a legacy behaviour..the reason that this was done was to attempt to prevent reconstructs in case that we have one domain which is inaccessible imo.. we could look into possibly changing this behaviour.
We should always try to reconstruct on any available domain, with the current master having the lowest priority.
Re-targeting to 3.3.3 since the bug is not resolved in 3.3.2 beta and is not blocking 3.3.2 release tracker (bug #1027349)
Patch should be backported to the ovirt-engine-3.3 branch, returning to POST.
This is an oVirt bug, not a RHEVM bug - it should be on MODIFIED until 3.3.3 is released.
Closing as 3.3.3 has been released.