Bug 1748825

Summary: Preserve (dynamic) IPv6 address when defining a bridge over an existing interface.
Product: Red Hat Enterprise Linux 8 Reporter: Edward Haas <edwardh>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 8.1CC: jiji, jishi, mburman, network-qe, wchadwic
Target Milestone: rc   
Target Release: 8.1   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: nmstate-0.0.8-14.el8 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2019-11-05 20:52:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
cmd and output none

Description Edward Haas 2019-09-04 09:05:46 UTC 
Description of problem:
In scenarios where the user (RHV in this case) defines a bridge over a nic/bond/vlan that already has a dynamic IPv6 address, it is expected that the address will be moved to the bridge without modifications.
Currently, this is not the default and it is not controllable from the nmstate API.

We need to change the default and possible consider allowing this to be controlled through some type of defaults (see one option proposal here: https://bugzilla.redhat.com/1743161

Version-Release number of selected component (if applicable):
0.0.8

How reproducible:
100%

Steps to Reproduce:
1. Define a dynamic IPv6 config on a nic or bond and make sure the address is provided from the server.
2. Define a bridge over the nic/bond with dynamic IPv6.
3. Check that the new address on the bridge is not identical to the one that was there before on the nic/bond.

Actual results:
IPv6 address is not preserved when moving from nic/bond/vlan to bridge.

Expected results:
IPv6 address should remain identical.

Additional info:
This is a blocker for RHV when the hosts have dynamic IPv6 enabled.
Comment 5 Gris Ge 2019-09-06 08:28:14 UTC 
Please be advised that NetworkManager need to be configured to use dhclient as DHCP client to achieve fix in this bug.

NetworkManager internal DHCP client bug is #1749358
Comment 8 Mingyu Shi 2019-09-16 09:54:19 UTC 
Created attachment 1615512 [details]
cmd and output
Comment 10 errata-xmlrpc 2019-11-05 20:52:18 UTC 
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.

https://access.redhat.com/errata/RHBA-2019:3347