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 788700

Summary: [VDSM] Failure to create mgmt network (rhevm) on a new Host with Bond.
Product: Red Hat Enterprise Linux 6 Reporter: zvi <zfridler>
Component: vdsmAssignee: Dan Kenigsberg <danken>
Status: CLOSED WONTFIX QA Contact: yeylon <yeylon>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.2CC: abaron, bazulay, iheim, srevivo, ykaul
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-02-09 15:44:04 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:    
Bug Blocks: 788902    
Attachments:
Description Flags
BE and VDSM logs none

Description zvi 2012-02-08 20:28:15 UTC
Description of problem:
Failure to create mgmt network (rhevm) with a bonded interface. 
VDSM installation fails to install a new Host with a bonded interfaces. 
The Host will be added to the Cluster, but will remain Non Operational, since the mgmt bridge wasn't created.
I think its not only a vds_bootstrap Bug because the Host was added to the Cluster:

vds_bootstrap.24472.log:Wed, 08 Feb 2012 21:44:58 ERROR    _getRHELBridgeParams Found bonding: bond0. This network configuration is not supported! Please configure rhevm bridge manually and re-install.


HOST with IP 10.35.102.33 bonded with eth1&eth2. see BE and VDSM logs attachment.


Version-Release number of selected component (if applicable):
3.0.112.6

How reproducible:


Steps to Reproduce:
1.GUI: Add a new Host with a bonded interfaces to the Cluster.
2.
3.
  
Actual results:
Failure to create rhevm MN (management network) 

Expected results:

mgmt network should be created and linked to the bond.

Additional info:

[root@navy-vds3 ~]# brctl show
bridge name	bridge id		STP enabled	interfaces
[root@navy-vds3 ~]# ifconfig bond0
bond0     Link encap:Ethernet  HWaddr 00:10:18:24:47:6F  
          inet addr:10.35.102.33  Bcast:10.35.102.255  Mask:255.255.255.0
          inet6 addr: fe80::210:18ff:fe24:476f/64 Scope:Link
          UP BROADCAST RUNNING MASTER MULTICAST  MTU:1500  Metric:1
          RX packets:2264 errors:0 dropped:0 overruns:0 frame:0
          TX packets:278 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:344661 (336.5 KiB)  TX bytes:60083 (58.6 KiB)

[root@navy-vds3 ~]# cat /proc/net/bonding/bond0
Ethernet Channel Bonding Driver: v3.6.0 (September 26, 2009)

Bonding Mode: fault-tolerance (active-backup)
Primary Slave: None
Currently Active Slave: eth1
MII Status: up
MII Polling Interval (ms): 100
Up Delay (ms): 0
Down Delay (ms): 0

Slave Interface: eth1
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:10:18:24:47:6f
Slave queue ID: 0

Slave Interface: eth2
MII Status: up
Speed: 1000 Mbps
Duplex: full
Link Failure Count: 0
Permanent HW addr: 00:14:5e:dd:08:8e
Slave queue ID: 0
[root@navy-vds3 ~]#

Comment 1 zvi 2012-02-08 20:32:09 UTC
Created attachment 560379 [details]
BE and VDSM logs

Comment 3 zvi 2012-02-09 15:44:04 UTC
the bridge should be created manually