Description of problem:
Engine does not report out-of-sync on ipv6-enabled network.
Version-Release number of selected component (if applicable):
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
the network remains in sync
the network should be out of sync
this functionality exists but was disabled due to ipv6 related bugs in vdsm\engine.
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.
Please make sure to test all permutations of configurations on host interfaces:
- ipv4 only
- ipv6 static configuration only
- ipv4 + ipv6 static
(In reply to eraviv from comment #2)
> Dear QE,
> Please make sure to test all permutations of configurations on host
> - ipv4 only
> - ipv6 static configuration only
> - ipv4 + ipv6 static
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.
-ipv4 only - check there are no regressions
- dual stack - my mistake
(In reply to eraviv from comment #4)
> -ipv4 only - check there are no regressions
> - dual stack - my mistake
Verified on - rhvm-188.8.131.52-0.1.el7.noarch
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.