Bug 1298534 - [SetupNetworks] attaching network with static boot protocol and IP cause the network to be un-synced
Summary: [SetupNetworks] attaching network with static boot protocol and IP cause the ...
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Network
Version: 3.6.2.5
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ovirt-3.6.2
: 3.6.2.6
Assignee: Alona Kaplan
QA Contact: Meni Yakove
URL:
Whiteboard:
Depends On:
Blocks: 1140850 1270807
TreeView+ depends on / blocked
 
Reported: 2016-01-14 11:41 UTC by Meni Yakove
Modified: 2016-02-18 11:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-02-18 11:03:18 UTC
oVirt Team: Network
Embargoed:
danken: ovirt-3.6.z?
myakove: planning_ack?
rule-engine: devel_ack+
rule-engine: testing_ack+

Attachments (Terms of Use)
engine log (3.15 MB, text/plain)
2016-01-14 11:41 UTC, Meni Yakove 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 52395 0 master MERGED engine: both null and empty gateway should be considered as no gateway 2016-01-19 08:28:19 UTC
oVirt gerrit 52396 0 ovirt-engine-3.6 MERGED engine: both null and empty gateway should be considered as no gateway 2016-01-19 08:44:18 UTC
oVirt gerrit 52397 0 ovirt-engine-3.6.2 MERGED engine: both null and empty gateway should be considered as no gateway 2016-01-19 08:45:38 UTC

Description Meni Yakove 2016-01-14 11:41:09 UTC 
Created attachment 1114757 [details]
engine log

Description of problem:
A network that attach to the host via SetupNetwork with static boot protocol and IP/Netmask ends up as a un-synced network.

Same results using netmask or prefix

Version-Release number of selected component (if applicable):
rhevm-3.6.2.5-0.1.el6.noarch

How reproducible:
100%

Steps to Reproduce:
1. Create network on DC and attach it to cluster
2. Attach the network to the host via SetupNetworks with boot protocol static, IP and netmask

Actual results:
The network is un-synced

Expected results:
The network is synced
Comment 1 Meni Yakove 2016-01-14 13:17:47 UTC 
The network is out of sync because the gateway is empty probably because of this fix https://gerrit.ovirt.org/#/c/51153/ (https://bugzilla.redhat.com/show_bug.cgi?id=1270688)
Comment 2 Red Hat Bugzilla Rules Engine 2016-01-17 12:24:53 UTC 
Bug tickets must have version flags set prior to targeting them to a release. Please ask maintainer to set the correct version flags and only then set the target milestone.
Comment 3 Michael Burman 2016-01-21 09:39:47 UTC 
Verified on - 3.6.2.6-0.1.el6
Note You need to log in before you can comment on or make changes to this bug.