RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

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.

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

Created attachment 1615512 [details]
cmd and output

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