Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 910490

Summary:	vdsm: connect to super vdsm failed due to fail in prepareForShutDown
Product:	Red Hat Enterprise Linux 6	Reporter:	Chris Pelland <cpelland>
Component:	vdsm	Assignee:	Yaniv Bronhaim <ybronhei>
Status:	CLOSED ERRATA	QA Contact:	Haim <hateya>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.3	CC:	abaron, bazulay, dron, hateya, iheim, ilvovsky, lpeer, sgrinber, thildred, ybronhei, yeylon, ykaul
Target Milestone:	rc	Keywords:	Regression, ZStream
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:	infra
Fixed In Version:	vdsm-4.10.2-1.4.el6	Doc Type:	Bug Fix
Doc Text:	Previously, if storage networking were interrupted, host connections to the super VDSM process would fail. This was due to a race condition that saw VDSM kill itself, respawn, unlink its socket, and try to connect to the socket it had just removed. Now the socket is left in place, and the new VDSM process can connect to the super VDSM process after respawning.	Story Points:	---
Clone Of:	910005	Environment:
Last Closed:	2013-02-25 19:09:25 UTC	Type:	Bug
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:	910005
Bug Blocks:

Comment 2 Dafna Ron 2013-02-18 10:10:57 UTC

verified on vdsm-4.10.2-1.5.el6.x86_64
although prepareForShutdown was stuck for a few seconds vdsm managed to restart

Comment 4 errata-xmlrpc 2013-02-25 19:09:25 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-0555.html