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 884722 - 3.1.z - 3.1.2 - SuperVdsm is not functional after proccesing an exception resulted in delete network operation.
Summary: 3.1.z - 3.1.2 - SuperVdsm is not functional after proccesing an exception res...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.3
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: ---
Assignee: Yaniv Bronhaim
QA Contact: Leonid Natapov
URL:
Whiteboard: infra
: 881730 918979 (view as bug list)
Depends On: 875486
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-12-06 15:58 UTC by Chris Pelland
Modified: 2018-12-01 15:53 UTC (History)
16 users (show)

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.
Clone Of:
Environment:
Last Closed: 2013-02-04 21:11:52 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Knowledge Base (Solution) 341473 0 None None None Never
Red Hat Product Errata RHBA-2013:0228 0 normal SHIPPED_LIVE vdsm bug fix update 2013-02-05 02:10:49 UTC

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. ***


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