Bug 1016118

Summary:	async between masterVersion : can't connect to StoragePool
Product:	[Retired] oVirt	Reporter:	Ohad Basan <obasan>
Component:	ovirt-engine-core	Assignee:	Liron Aravot <laravot>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Aharon Canan <acanan>
Severity:	high	Docs Contact:
Priority:	medium
Version:	3.3	CC:	acathrow, amureini, eedri, ewarszaw, iheim, laravot, tnisan, yeylon
Target Milestone:	---
Target Release:	3.3.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	storage
Fixed In Version:	ovirt-3.3.3-beta1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:
Clones:	1044897 (view as bug list)		Environment:
Last Closed:	2014-02-14 09:57:21 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:
Bug Blocks:	1044897

Description Ohad Basan 2013-10-07 14:37:50 UTC

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

Comment 6 Liron Aravot 2013-11-05 14:35:40 UTC

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.

Comment 7 Allon Mureinik 2013-11-06 18:48:24 UTC

We should always try to reconstruct on any available domain, with the current master having the lowest priority.

Comment 8 Sandro Bonazzola 2013-11-28 15:34:16 UTC

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)

Comment 10 Allon Mureinik 2013-12-12 15:51:24 UTC

Patch should be backported to the ovirt-engine-3.3 branch, returning to POST.

Comment 11 Allon Mureinik 2013-12-22 12:18:44 UTC

This is an oVirt bug, not a RHEVM bug - it should be on MODIFIED until 3.3.3 is released.

Comment 12 Sandro Bonazzola 2014-02-14 09:57:21 UTC

Closing as 3.3.3 has been released.