Bug 984028 - [RHEVM][backend][vdsm][multiple gateways] Keep ovirt management as default in the main routing table always
[RHEVM][backend][vdsm][multiple gateways] Keep ovirt management as default in...
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: vdsm (Show other bugs)
x86_64 Linux
unspecified Severity high
: ---
: 3.3.0
Assigned To: Assaf Muller
Martin Pavlik
: 989237 (view as bug list)
Depends On:
Blocks: 618636 1019461
  Show dependency treegraph
Reported: 2013-07-12 10:49 EDT by Martin Pavlik
Modified: 2016-02-10 14:48 EST (History)
14 users (show)

See Also:
Fixed In Version: is12
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 994523 (view as bug list)
Last Closed: 2014-01-21 11:28:11 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: Network
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
amuller: needinfo-

Attachments (Terms of Use)
log_collector (8.54 MB, application/x-xz)
2013-07-12 10:49 EDT, Martin Pavlik
no flags Details

External Trackers
Tracker ID Priority Status Summary Last Updated
oVirt gerrit 17575 None None None Never
oVirt gerrit 17844 None None None Never

  None (edit)
Description Martin Pavlik 2013-07-12 10:49:49 EDT
Created attachment 772752 [details]

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)
Comment 1 Assaf Muller 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.
Comment 2 GenadiC 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 3 Dan Kenigsberg 2013-08-22 18:27:21 EDT
*** Bug 989237 has been marked as a duplicate of this bug. ***
Comment 5 Meni Yakove 2013-09-01 02:15:42 EDT
Comment 6 Charlie 2013-11-27 19:30:32 EST
This bug is currently attached to errata RHBA-2013:15291. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to 
minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.

Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:

* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')

Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.

For further details on the Cause, Consequence, Fix, Result format please refer to:


Thanks in advance.
Comment 7 errata-xmlrpc 2014-01-21 11:28:11 EST
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.


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