Bug 1670341 - [Default route] - Engine allows to set network as default route role without DG, but complains about it
Summary: [Default route] - Engine allows to set network as default route role without ...
Keywords:
Status: CLOSED DEFERRED
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 4.3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: ---
Assignee: eraviv
QA Contact: Michael Burman
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-01-29 10:50 UTC by Michael Burman
Modified: 2022-03-21 12:22 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-03-21 12:22:09 UTC
oVirt Team: Network


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHV-37706 0 None None None 2022-02-02 09:25:34 UTC

Description Michael Burman 2019-01-29 10:50:04 UTC
Description of problem:
[Default route] - Engine allows to set network as default route role without DG, but complains about it.

Engine allow the user/admin to set a network with a default route role with only IPv4/IPv6 address + subnet/prefix, but without default gateway, which is actually required for the default route role. 

Engine doesn't validate the default gateway, but it does complains about it and show the network as out-of-sync because of default route property, which is also misleading. 

Version-Release number of selected component (if applicable):
4.3.0-0.8.rc2.el7

How reproducible:
100%

Steps to Reproduce:
1. Set a non-mgmt network with default route role
2. Attach the network to the host with only IPv4 or IPv6 address and subnet. Without default gateway

Actual results:
Network is out-of-sync

Expected results:
1. Or validate that network has a default gateway if it's a default route role
2. Or don't complain about it, don't show the network as out-of-sync

Additional info:
Default gateway is required for default route role, for both IPv4 and IPv6.

Comment 4 Martin Perina 2022-03-21 12:22:09 UTC
The use case is quite corner case and proper fix would requires too much work, closing as deferred


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