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 823248

Summary: [ovirt] [vdsm] exception in getVdsCaps in case bridge is renamed and vdsm is not resarted
Product: Red Hat Enterprise Linux 6 Reporter: Haim <hateya>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED DUPLICATE QA Contact: Haim <hateya>
Severity: medium Docs Contact:
Priority: medium    
Version: 6.3CC: abaron, acathrow, bazulay, dyasny, iheim, lpeer, mgoldboi, yeylon, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: infra, network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-07 08:31:11 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:

Description Haim 2012-05-20 10:52:02 UTC
Description of problem:

- host is operational configured with bridge name = rhevm (name is not important)
- renamed bridge name from rhevm to ovirtmgmt
- restart network service 
- vdsm fails to respond to getVdsCaps and fails with nasty exception:  


Thread-870::DEBUG::2012-05-20 13:21:43,327::BindingXMLRPC::849::vds::(wrapper) client [10.35.97.174]::call getCapabilities with () {}
Thread-870::ERROR::2012-05-20 13:21:43,335::BindingXMLRPC::864::vds::(wrapper) unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/BindingXMLRPC.py", line 854, in wrapper
    res = f(*args, **kwargs)
  File "/usr/share/vdsm/BindingXMLRPC.py", line 263, in getCapabilities
    ret = api.getCapabilities()
  File "/usr/share/vdsm/API.py", line 1075, in getCapabilities
    c = caps.get()
  File "/usr/share/vdsm/caps.py", line 225, in get
    caps.update(netinfo.get())
  File "/usr/lib/python2.6/site-packages/vdsm/netinfo.py", line 243, in get
    d['networks'][netname] = { 'ports': ports(netname),
  File "/usr/lib/python2.6/site-packages/vdsm/netinfo.py", line 92, in ports
    return os.listdir('/sys/class/net/' + bridge + '/brif')
OSError: [Errno 2] No such file or directory: '/sys/class/net/rhevm/brif'


mitigation: restart vdsm service

Comment 1 Haim 2012-05-20 10:53:18 UTC
latest vdsm on master: f43fb7de2c3fd24f0520b7f444a3318ef28cc915

Comment 2 Dan Kenigsberg 2012-08-01 13:47:53 UTC
Yep, if `virsh net-list` show a bridged vdsm network without an actual bridge implementation, we're in trouble.

Since it was open by Red Hat QE and affecting RHEV, moving the tracking downstream.

Comment 4 lpeer 2012-08-07 08:31:11 UTC

*** This bug has been marked as a duplicate of bug 840594 ***