Bug 923443 - Gateway is not defined after bonding the RHEVM interface.
Summary: Gateway is not defined after bonding the RHEVM interface.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine-webadmin-portal
Version: 3.1.3
Hardware: x86_64
OS: Linux
urgent
high
Target Milestone: ---
: 3.2.0
Assignee: Alona Kaplan
QA Contact: Martin Pavlik
URL:
Whiteboard: network
Depends On:
Blocks: 958536
TreeView+ depends on / blocked
 
Reported: 2013-03-19 20:38 UTC by Josh Carter
Modified: 2022-07-09 06:03 UTC (History)
15 users (show)

Fixed In Version: sf14
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 958536 (view as bug list)
Environment:
Last Closed: 2013-06-10 21:37:16 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-47122 0 None None None 2022-07-09 06:03:44 UTC
Red Hat Product Errata RHSA-2013:0888 0 normal SHIPPED_LIVE Moderate: Red Hat Enterprise Virtualization Manager 3.2 update 2013-06-11 00:55:41 UTC
oVirt gerrit 13790 0 None None None Never

Description Josh Carter 2013-03-19 20:38:19 UTC
Description of problem:
When configuration a vlan tagged rhevm network interface for a bond the gateway is not carried over and is defined as 0.0.0.0 which brings the hypervisor off the network. 

2013-02-26 10:38:58,331 INFO  [org.ovirt.engine.core.vdsbroker.vdsbroker.SetupNetworksVDSCommand] (ajp-/127.0.0.1:8702-8) [4451f362] START, SetupNetworksVDSC
ommand(HostName = cl3-d14-p1c1n1, HostId = e50fd8da-8039-11e2-b995-002590a5c988, force=false, checkConnectivity=true, conectivityTimeout=120,
        networks=[rhevm {id=11b19869-4040-46fb-891b-d4434a70c4b9, description=Management Network, subnet=null, gateway=null, type=null, vlan_id=258, stp=fals
e, storage_pool_id=b6af4cd3-2862-49c1-8014-781da84b5756, mtu=0, vmNetwork=true, cluster=network_cluster {id={clusterId=null, networkId=null}, status=Operatio
nal, is_display=false, required=true}}],
        bonds=[bond0 {id=87144bf3-75f7-4e53-aa6f-9e4fd60eb5ff, vdsId=e50fd8da-8039-11e2-b995-002590a5c988, name=bond0, macAddress=00:00:00:00:00:00, networkName=null, bondOptions=mode=4, bootProtocol=None, address=, subnet=, gateway=null, mtu=1500, bridged=false, type=2, networkImplementationDetails=null}],
        interfaces=[eth0 {id=04a1e4fb-4f71-40d3-b737-e35c88880f0c, vdsId=e50fd8da-8039-11e2-b995-002590a5c988, name=eth0, macAddress=00:25:90:97:DF:AE, networkName=null, bondName=bond0, bootProtocol=None, address=, subnet=, gateway=null, mtu=1500, bridged=false, speed=1000, type=0, networkImplementationDetails=null},
                eth1 {id=dce7c8c4-1887-4401-8b68-4af4532c2f3a, vdsId=e50fd8da-8039-11e2-b995-002590a5c988, name=eth1, macAddress=00:25:90:97:DF:AF, networkName=null, bondName=bond0, bootProtocol=None, address=, subnet=, gateway=null, mtu=1500, bridged=false, speed=0, type=0, networkImplementationDetails=null},
                bond0 {id=87144bf3-75f7-4e53-aa6f-9e4fd60eb5ff, vdsId=e50fd8da-8039-11e2-b995-002590a5c988, name=bond0, macAddress=00:00:00:00:00:00, networkName=null, bondOptions=mode=4, bootProtocol=None, address=, subnet=, gateway=null, mtu=1500, bridged=false, type=2, networkImplementationDetails=null},
                bond0.258 {id=null, vdsId=e50fd8da-8039-11e2-b995-002590a5c988, macAddress=null, networkName=rhevm, vlanId=258, bonded=null, bondName=null, bondOptions=null, bootProtocol=StaticIp, address=172.16.16.1, subnet=255.255.252.0, gateway=null, mtu=1500, bridged=true, speed=null, type=2, networkImplementationDetails=null}],
        removedNetworks=[],
        removedBonds=[]), log id: 2b5574c8


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

rhevm-3.1.0-50.el6ev.noarch


How reproducible:
Customer is able to recreate the problem at any given time. 

http://www.screencast.com/t/qfRTsZYr

Steps to Reproduce:
1.http://www.screencast.com/t/qfRTsZYr
2.
3.
  
Actual results:

Bond is created without a valid gateway. 

Expected results:

Bond should come up successful with a valid gateway. 

Additional info:

Comment 11 Martin Pavlik 2013-04-26 15:15:15 UTC
works in sf14

Thread-146::DEBUG::2013-04-26 17:12:16,352::BindingXMLRPC::913::vds::(wrapper) client [10.34.63.68]::call setupNetworks with ({'vnet1': {'remove': 'true'}, 'rhevm': {'vlan': '172', 'ipaddr': '10.34.67.90', 'netmask': '255.255.255.224', 'bonding': 'bond0', 'STP': 'no', 'bridged': 'true', 'gateway': '10.34.67.94'}}, {'bond0': {'nics': ['em1', 'em2'], 'options': 'mode=1 miimon=100'}}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}) {} flowID [4042036e]

Comment 17 errata-xmlrpc 2013-06-10 21:37:16 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/RHSA-2013-0888.html


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