Bug 788700 - [VDSM] Failure to create mgmt network (rhevm) on a new Host with Bond.
Summary: [VDSM] Failure to create mgmt network (rhevm) on a new Host with Bond.
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: vdsm
Version: 6.2
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: Dan Kenigsberg
QA Contact: yeylon@redhat.com
URL:
Whiteboard:
Depends On:
Blocks: 788902
TreeView+ depends on / blocked
 
Reported: 2012-02-08 20:28 UTC by zvi
Modified: 2016-04-18 06:43 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-02-09 15:44:04 UTC
Target Upstream Version:


Attachments (Terms of Use)
BE and VDSM logs (1.00 MB, application/x-gzip)
2012-02-08 20:32 UTC, zvi
no flags Details

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


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