Bug 884722

Summary:	3.1.z - 3.1.2 - SuperVdsm is not functional after proccesing an exception resulted in delete network operation.
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Pelland <cpelland>
Component:	vdsm	Assignee:	Yaniv Bronhaim <ybronhei>
Status:	CLOSED ERRATA	QA Contact:	Leonid Natapov <lnatapov>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.3	CC:	abaron, bazulay, chetan, cpelland, dornelas, hateya, iheim, ilvovsky, lpeer, mahendra_takwale, mavital, myakove, pm-eus, spandura, ybronhei, ykaul
Target Milestone:	rc	Keywords:	ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	infra
Fixed In Version:	vdsm-4.9.6-45.1	Doc Type:	Bug Fix
Doc Text:	SuperVdsm (svdsm) was not functional after processing an exception which caused a network delete operation. Consequently, storage and network actions which required svdsm permissions failed. With this update, when svdsm recognizes that the vdsm pid does not exist, it sends a SIGKILL signal and terminates itself. The exception which causes the svdsm to malfunction does not occur.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2013-02-04 21:11:52 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	875486
Bug Blocks:

Description Chris Pelland 2012-12-06 15:58:27 UTC

This bug has been copied from bug #875486 and has been proposed
to be backported to 6.3 z-stream (EUS).

Comment 4 Barak 2012-12-06 16:14:20 UTC

upstream patch 

http://gerrit.ovirt.org/#/c/8600

Comment 6 Haim 2012-12-19 12:24:04 UTC

*** Bug 881730 has been marked as a duplicate of this bug. ***

Comment 8 Leonid Natapov 2013-01-17 10:00:44 UTC

vdsm-4.9.6-45.1.el6_3.x86_64
Fixed. 
Created new network on the host,after that deleted config file from the host and tried to operate with the network. got an exception. after returning the config file things are back operate normally.

Comment 10 errata-xmlrpc 2013-02-04 21:11:52 UTC

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.

http://rhn.redhat.com/errata/RHBA-2013-0228.html

Comment 11 Haim 2013-03-21 17:40:04 UTC

*** Bug 918979 has been marked as a duplicate of this bug. ***