Bug 994523 - [vdsm][multiple gateways] Keep ovirt management as default in the main routing table always
Summary: [vdsm][multiple gateways] Keep ovirt management as default in the main routin...
Alias: None
Product: oVirt
Classification: Retired
Component: vdsm
Version: 3.3
Hardware: x86_64
OS: Linux
Target Milestone: ---
: 3.3
Assignee: Assaf Muller
QA Contact: Haim
Whiteboard: network
Depends On:
Blocks: 618636 918494 990854
TreeView+ depends on / blocked
Reported: 2013-08-07 12:49 UTC by Assaf Muller
Modified: 2013-09-23 07:31 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of: 984028
Last Closed: 2013-09-23 07:31:37 UTC
oVirt Team: ---

Attachments (Terms of Use)

System ID Priority Status Summary Last Updated
oVirt gerrit 17575 None None None Never
oVirt gerrit 17844 None None None Never

Description Assaf Muller 2013-08-07 12:49:36 UTC
+++ This bug was initially created as a clone of Bug #984028 +++

Description of problem:
If logical network which had configured default gateway is removed, the host has no default gateway

Version-Release number of selected component (if applicable):
oVirt Engine Version: 3.3.0-0.2.master.20130710172219.git240a5ed.fc18 

How reproducible:

Steps to Reproduce:
1. Create a logical network (NET1), attach it to cluster and host
2. Hosts -> your host ->  Network Interfaces -> setup Host networks
3. Attach NET1 to host, configure static IP, netmask , gateway (apply changes)
4. remove NET1 from host via setup Host networks (apply changes)

Actual results:
no default route on host

Expected results:
default route pointing towards ovirtmgmt gateway

Additional info:

before adding logical network
[root@dell-r210ii-07 ~] # IP are
default via dev ovirtmgmt dev ovirtmgmt  proto kernel  scope link  src dev em2  scope link  metric 1003 dev ovirtmgmt  scope link  metric 1012 

after adding logical network
[root@dell-r210ii-07 ~]# ip r
default via dev net_67_0 dev ovirtmgmt  proto kernel  scope link  src dev net_67_0  proto kernel  scope link  src dev ovirtmgmt  scope link  metric 1012 dev net_67_0  scope link  metric 1013 

logical network removed
[root@dell-r210ii-07 ~]# ip r dev ovirtmgmt  proto kernel  scope link  src dev em2  scope link  metric 1003 dev ovirtmgmt  scope link  metric 1012 

Thread-46::DEBUG::2013-07-12 16:14:40,427::fileSD::238::Storage.Misc.excCmd::(getReadDelay) SUCCESS: <err> = '0+1 records in\n0+1 records out\n470 bytes (470 B) copied, 0.000396517 s, 1.2 MB/s\n'; <rc> = 0
Thread-2100::DEBUG::2013-07-12 16:14:49,713::BindingXMLRPC::946::vds::(wrapper) client []::call setupNetworks with ({'net_67_0': {'remove': 'true'}}, {}, {'connectivityCheck': 'true', 'connectivityTimeout': 120}) {}
Thread-2101::DEBUG::2013-07-12 16:14:49,715::BindingXMLRPC::946::vds::(wrapper) client []::call ping with () {}
Thread-2101::DEBUG::2013-07-12 16:14:49,715::BindingXMLRPC::953::vds::(wrapper) return ping with {'status': {'message': 'Done', 'code': 0}}
Thread-2102::DEBUG::2013-07-12 16:14:50,220::BindingXMLRPC::946::vds::(wrapper) client []::call ping with () {}
Thread-2102::DEBUG::2013-07-12 16:14:50,220::BindingXMLRPC::953::vds::(wrapper) return ping with {'status': {'message': 'Done', 'code': 0}}
Thread-46::DEBUG::2013-07-12 16:14:50,438::fileSD::238::Storage.Misc.excCmd::(getReadDelay) '/usr/bin/dd iflag=direct if=/rhev/data-center/mnt/ bs=4096 count=1' (cwd None)

--- Additional comment from Assaf Muller on 2013-07-14 11:00:17 EDT ---

This bug existed in the product since its inception. For example on a 3.1/3.2 setup, if a secondary (non-ovirtmgmt) network got a gateway through DHCP and was then detached, the host was left without a default gateway in its main routing table.

However, the multiple gateways feature introduced in 3.3 makes this bug more apparent.

One proposed solution is: During setupNetworks the engine should mark the management network, or the network which has the host's gateway which should be kept in the main routing table. Then we can make sure that the host will keep that network's gateway in its main table.

Another solution would be for VDSM internally to mark the management network according to its name, and keep that network's gateway in the host's main routing table.

Keep in mind that in case that the host is configured properly (using the multiple gateways feature), then the feature fixed half of the bug. Before 3.3, if the secondary network had a gateway through DHCP and was then removed, then the gateway was removed from the main routing table and the host would be completely unreachable from outside of its other subnets. Now, with 3.3, the host responds to pings to its other NICs (Even from outside of its subnets) but traffic originating FROM the host to destinations outside of its subnets will be dropped at the host.

--- Additional comment from GenadiC on 2013-07-31 06:59:06 EDT ---

Another scenario for the problem:
1) Put network red on the host (which is SPM) with SN (ip:, dg:
2) Put the Host in Maintenance
3) Activate Host
Result: Host can't connect to the storage as it tries to go through

Comment 1 Itamar Heim 2013-08-21 16:40:00 UTC
as RC is built, moving to ON_QA (hopefully did not catch incorrect bugs when doing this)

Comment 2 Itamar Heim 2013-09-23 07:31:37 UTC
closing as this should be in 3.3 (doing so in bulk, so may be incorrect)

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