Bug 1607118

Summary:	[IPv6] - Engine does not report out-of-sync on ipv6-enabled network
Product:	[oVirt] ovirt-engine	Reporter:	eraviv
Component:	BLL.Network	Assignee:	eraviv
Status:	CLOSED CURRENTRELEASE	QA Contact:	Michael Burman <mburman>
Severity:	low	Docs Contact:
Priority:	medium
Version:	4.2.2	CC:	bugs, danken, dholler, eraviv, mburman
Target Milestone:	ovirt-4.3.1	Flags:	rule-engine: ovirt-4.3+
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	ovirt-engine-4.3.1.1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-03-01 10:17:47 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1467332
Bug Blocks:

Description eraviv 2018-07-22 07:59:36 UTC

Description of problem:
Engine does not report out-of-sync on ipv6-enabled network.

Version-Release number of selected component (if applicable):
ovirt-engine 4.3-master

How reproducible:
100%

Steps to Reproduce:
1. create network with ipv6 config on host
2. change the ipv6 boot protocol on the host bridge
3. refresh host capabilities from engine

Actual results:
the network remains in sync

Expected results:
the network should be out of sync

Additional info:
see NetworkInSyncWithVdsNetworkInterface.java#L76-82:
this functionality exists but was disabled due to ipv6 related bugs in vdsm\engine.

Comment 1 Sandro Bonazzola 2019-01-28 09:34:03 UTC

This bug has not been marked as blocker for oVirt 4.3.0.
Since we are releasing it tomorrow, January 29th, this bug has been re-targeted to 4.3.1.

Comment 2 eraviv 2019-02-24 07:32:02 UTC

Dear QE,

Please make sure to test all permutations of configurations on host interfaces:
- ipv4 only
- ipv6 static configuration only
- ipv4 + ipv6 static


Thanks

Comment 3 Michael Burman 2019-02-24 07:57:23 UTC

(In reply to eraviv from comment #2)
> Dear QE,
> 
> Please make sure to test all permutations of configurations on host
> interfaces:
> - ipv4 only
> - ipv6 static configuration only
> - ipv4 + ipv6 static
> 
> 
> Thanks

Eitan, i don't follow. IPv4? what i need to test here? you touched only ipv6 i hope. Why i need to check ipv4 out-of-sync? 
We don't support dual stack, what you want to test with ipv4 + ipv6 static? 
This wasn't part of the changes planned.

Comment 4 eraviv 2019-02-24 08:31:27 UTC

correction:
-ipv4 only - check there are no regressions
- dual stack - my mistake

Comment 5 Michael Burman 2019-02-26 12:26:51 UTC

(In reply to eraviv from comment #4)
> correction:
> -ipv4 only - check there are no regressions
> - dual stack - my mistake

ACK

Verified on - rhvm-4.3.1.1-0.1.el7.noarch

Comment 6 Sandro Bonazzola 2019-03-01 10:17:47 UTC

This bugzilla is included in oVirt 4.3.1 release, published on February 28th 2019.

Since the problem described in this bug report should be
resolved in oVirt 4.3.1 release, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.