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.

Created attachment 598495 [details]
vdsm.log

Description of problem:
When bridge on virsh and on the host (brctl) do not match then the host is in unassigned status. 
Get error in vdsm log about missing file in /sys/class/net
OSError: [Errno 2] No such file or directory: '/sys/class/net/vm_net3/brif'

[root@orchid-vds2 net]# vdsClient -s 0 getVdsCaps
Unexpected exception


Version-Release number of selected component (if applicable):
vdsm-4.9.6-21.0.el6_3.x86_64

How reproducible:
100%

Steps to Reproduce:
1.Attach network to interface on host.
2.on the host delete the newly created bridge - brctl delbr
3.Switch the host to maintenance.
4.Activate the host.
  
Actual results:
Host is in unassigned.

Expected results:
Host should be in non-operational status.

That's pretty bad - we have to be more robust.

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

Submitted patch:

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

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

Verified on vdsm-4.9.6-29.0.el6_3.x86_64

We have pretty much the same problem with bridgeless networks, too. If libvirt's network definition refers to a vlan device (or bond, or nic) that happen to be missing, getVdsCaps break into pieces.

Reopening to fix the cases above pointed out by Dan Kenigsberg.

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/RHSA-2012-1508.html