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 2073926 - Lose static IPv6 address after reapply decice
Summary: Lose static IPv6 address after reapply decice
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.6
Hardware: x86_64
OS: Linux
urgent
urgent
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: David Jaša
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-04-11 07:02 UTC by Gris Ge
Modified: 2022-11-08 11:22 UTC (History)
9 users (show)

Fixed In Version: NetworkManager-1.39.2-1.el8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-08 10:10:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
Reproducer script (411 bytes, application/x-shellscript)
2022-04-11 07:29 UTC, Gris Ge 		no flags Details
NetworkManager trace log (201.71 KB, text/plain)
2022-04-11 07:30 UTC, Gris Ge 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-118507 0 None None None 2022-04-11 07:13:03 UTC
Red Hat Product Errata RHBA-2022:7680 0 None None None 2022-11-08 10:10:55 UTC

Description Gris Ge 2022-04-11 07:02:55 UTC 
Description of problem:

The `nmcli device reapply eth1` will lose manual static IPv6 address.


Version-Release number of selected component (if applicable):
NetworkManager-1.39.0-30132.copr.0f2708f86a.el8.x86_64


How reproducible:
100%

Steps to Reproduce:
1. sudo ./bug.sh
2.
3.

Actual results:

Static IPv6 address gone.

Expected results:

Static IPv6 address still exist.

Additional info:

The `NetworkManager-1.37.3-1.el8.x86_64` has not such problem.
Comment 1 Gris Ge 2022-04-11 07:29:05 UTC 
Created attachment 1871714 [details]
Reproducer script
Comment 2 Gris Ge 2022-04-11 07:30:12 UTC 
Created attachment 1871715 [details]
NetworkManager trace log
Comment 3 Thomas Haller 2022-04-11 09:50:00 UTC 
fixed by https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/commit/7f427ac4e6711fafaee5a3ab76a006f92e122b00

We require a CI test for this.


Thanks for the report!!
Comment 4 Gris Ge 2022-04-11 11:35:44 UTC 
I personally dislike commit without test case proving issue reproduced and fixed.
Comment 5 Gris Ge 2022-04-11 13:30:06 UTC 
Nmstate CI is passing now with NetworkManager-1.39.0-30134.copr.4c67970e4c.el8.x86_64

https://github.com/nmstate/nmstate/actions/runs/2148485310
Comment 6 Thomas Haller 2022-04-11 16:46:13 UTC 
(In reply to Gris Ge from comment #4)
> I personally dislike commit without test case proving issue reproduced and
> fixed.

- CI test will be added (which is why the rhbz is in "POST" and not "CLOSED(Upstream)").

- I tested it manually.

- apparently you have a CI test, which is how you found this.
Comment 7 Gris Ge 2022-04-20 06:00:38 UTC 
Hi Thomas,

Our CI found the failure again on NetworkManager-1.39.1-30183.copr.a1ff31db3b.el8.x86_64

https://github.com/nmstate/nmstate/runs/6087795273?check_suite_focus=true
Nm log: https://github.com/nmstate/nmstate/suites/6182721693/artifacts/217326126
Comment 8 Thomas Haller 2022-04-20 08:42:40 UTC 
(In reply to Gris Ge from comment #7) 
> Our CI found the failure again on
> NetworkManager-1.39.1-30183.copr.a1ff31db3b.el8.x86_64
> 
> https://github.com/nmstate/nmstate/runs/6087795273?check_suite_focus=true
> Nm log:
> https://github.com/nmstate/nmstate/suites/6182721693/artifacts/217326126

The link to the log seems not to work. How to find the log?
It would be good to attach it.
Comment 9 Thomas Haller 2022-04-20 19:38:08 UTC 
I am gonna move this forward to errata/ON_QA. This will also help QA to add a CI test for this.

As of comment 7, there seems to be still a problem. If that verifies, we can go back to ASSIGNED afterwards.
Comment 10 Gris Ge 2022-04-25 03:57:28 UTC 
Somehow the test artifacts expired after 5 days.

I will upload logs next time I see this issue happen again in the CI.
Comment 13 David Jaša 2022-05-23 20:38:49 UTC 
(In reply to Gris Ge from comment #7)
> Hi Thomas,
> 
> Our CI found the failure again on
> NetworkManager-1.39.1-30183.copr.a1ff31db3b.el8.x86_64
> 
> https://github.com/nmstate/nmstate/runs/6087795273?check_suite_focus=true
> Nm log:
> https://github.com/nmstate/nmstate/suites/6182721693/artifacts/217326126

When verifying, I found that when running the commands manually, static IP is present after reapply but when using Gris's reproducer script, it isn't there. After adding one 'sleep 1' and looking at IPs again, it shows up as expected:
# ./bug2073926_repro.sh ; rpm -q NetworkManager
Connection 'dummy1' (418020cc-9497-421b-a5f0-da905ae28822) successfully deleted.
Connection 'dummy1' (8a0a307a-ccc9-477f-9e15-fc2d39730267) successfully added.
Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/12)
11: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 66:3d:c7:dc:c7:04 brd ff:ff:ff:ff:ff:ff
    inet 192.0.2.251/24 brd 192.0.2.255 scope global noprefixroute dummy1
       valid_lft forever preferred_lft forever
    inet6 2001:db8:1::1/128 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::84db:c78a:8ccd:abc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever
Connection successfully reapplied to device 'dummy1'.
After reapply
11: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 66:3d:c7:dc:c7:04 brd ff:ff:ff:ff:ff:ff
    inet 192.0.2.251/24 brd 192.0.2.255 scope global noprefixroute dummy1
       valid_lft forever preferred_lft forever
After 1 more second
11: dummy1: <BROADCAST,NOARP,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default qlen 1000
    link/ether 66:3d:c7:dc:c7:04 brd ff:ff:ff:ff:ff:ff
    inet 192.0.2.251/24 brd 192.0.2.255 scope global noprefixroute dummy1
       valid_lft forever preferred_lft forever
    inet6 2001:db8:1::1/128 scope global noprefixroute 
       valid_lft forever preferred_lft forever
    inet6 fe80::84db:c78a:8ccd:abc/64 scope link noprefixroute 
       valid_lft forever preferred_lft forever


NetworkManager-1.39.5-1.el9.x86_64
Comment 15 errata-xmlrpc 2022-11-08 10:10:31 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-2022:7680
Note You need to log in before you can comment on or make changes to this bug.