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.
Bug 1848888 - NM.Client cache for ipv6 address is not updated for after worker interface been assigned to parent interface
Summary: NM.Client cache for ipv6 address is not updated for after worker interface be...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.4
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: rc
: 8.0
Assignee: Beniamino Galvani
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-06-19 07:36 UTC by Gris Ge
Modified: 2020-11-04 01:51 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.26.0-0.2.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-11-04 01:50:15 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Reproduce script (2.74 KB, text/x-python)
2020-06-19 07:36 UTC, Gris Ge
no flags Details
System logs with NM trace enabled (NetworkManager-1.27.0-26095.92208ebd1f.el8.x86_64) (206.08 KB, text/plain)
2020-06-19 07:42 UTC, Gris Ge
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:4499 0 None None None 2020-11-04 01:50:36 UTC

Description Gris Ge 2020-06-19 07:36:25 UTC
Created attachment 1698053 [details]
Reproduce script

Description of problem:

When dummy1 been enslaved to bridge `brtest0`, dummy1 lose it's IPv6 link
local address. But the `NM.Client` cache still holding the old link local
address.

Version-Release number of selected component (if applicable):
NetworkManager-1.27.0-26090.56b15ca0b6.el8.x86_64

How reproducible:
100%

Steps to Reproduce:
1. sudo ./nm_slave_ip.py
2.
3.

Actual results:

The output contains:

dummy1 {'enabled': True, 'dhcp': False, 'autoconf': False, 'address': [{'ip': 'fe80::80b4:3aff:fef9:530a', 'prefix-length': 64}]}


Expected results:

The output should showing dummy1 has no IPv6 address any more.

Additional info:

Comment 1 Gris Ge 2020-06-19 07:42:37 UTC
Created attachment 1698055 [details]
System logs with NM trace enabled (NetworkManager-1.27.0-26095.92208ebd1f.el8.x86_64)

Comment 2 Beniamino Galvani 2020-06-26 13:47:01 UTC
Upstream merge request:

https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/551

Comment 11 errata-xmlrpc 2020-11-04 01:50:15 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 (NetworkManager bug fix and enhancement update), 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-2020:4499


Note You need to log in before you can comment on or make changes to this bug.