Bug 1185050 – failure of master migration on deactivation will leave domain locked

Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.

Bug 1185050 - failure of master migration on deactivation will leave domain locked

Summary:	failure of master migration on deactivation will leave domain locked

Status:	CLOSED ERRATA

Aliases:	None

Product:	Red Hat Enterprise Virtualization Manager
Classification:	Red Hat
Component:	ovirt-engine (Show other bugs)
Sub Component:
Version:	3.5.0
Hardware:	Unspecified Unspecified

Priority	unspecified Severity urgent
Target Milestone:	---
Target Release:	3.5.1
Assigned To:	Liron Aravot
QA Contact:	lkuchlan
Docs Contact:

URL:
Whiteboard:	storage
Keywords:	ZStream

Depends On:	1184927
Blocks:	1193058 1197441
	Show dependency tree / graph

Reported:	2015-01-22 14:23 EST by rhev-integ
Modified:	2016-02-10 13:21 EST (History)
CC List:	11 users (show)

See Also:
Fixed In Version:	org.ovirt.engine-root-3.5.1-1
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:	1184927
Environment:
Last Closed:	2015-04-28 14:44:56 EDT
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	Storage
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Flags:	ylavi: Triaged+

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

External Trackers
Tracker	ID	Priority	Status	Summary	Last Updated
oVirt gerrit	37201	master	MERGED	core: domain might remain locked on deactivation	Never
oVirt gerrit	37233	ovirt-engine-3.5	MERGED	core: domain might remain locked on deactivation	Never
Red Hat Product Errata	RHSA-2015:0888	normal	SHIPPED_LIVE	Moderate: Red Hat Enterprise Virtualization Manager 3.5.1 update	2015-04-28 18:40:04 EDT

Groups: None (edit)

Comment 2 lkuchlan 2015-03-02 04:05:37 EST

Testing using vdsm-4.16.12-2.el7ev, rhevm-3.5.1-0.1.el6ev

Comment 3 errata-xmlrpc 2015-04-28 14:44:56 EDT

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.

https://rhn.redhat.com/errata/RHSA-2015-0888.html

Note You need to log in before you can comment on or make changes to this bug.