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 2151426 - [RHEL8] Reapply does not updating IPv4 address in desired order
Summary: [RHEL8] Reapply does not updating IPv4 address in desired order
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 8
Classification: Red Hat
Component: NetworkManager
Version: 8.7
Hardware: x86_64
OS: Linux
high
high
Target Milestone: rc
: 8.8
Assignee: Fernando F. Mancera
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks: 2151428
TreeView+ depends on / blocked
 
Reported: 2022-12-07 04:03 UTC by Gris Ge
Modified: 2023-02-08 08:39 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
: 2151428 (view as bug list)
Environment:
Last Closed: 2022-12-20 09:55:39 UTC
Type: Bug
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Reproducer script (822 bytes, application/x-shellscript)
2022-12-07 04:03 UTC, Gris Ge
no flags Details
NetworkManager trace log (359.24 KB, text/plain)
2022-12-07 04:04 UTC, Gris Ge
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NMT-256 0 None None None 2023-02-08 08:39:25 UTC
Red Hat Issue Tracker RHELPLAN-141511 0 None None None 2022-12-07 04:07:01 UTC

Description Gris Ge 2022-12-07 04:03:29 UTC
Created attachment 1930701 [details]
Reproducer script

Description of problem:

The `nmcli d reapply <connection_name>` does not update IPv4 address as desired.

Version-Release number of selected component (if applicable):
NetworkManager-1.40.0-4.el8_7.x86_64
NetworkManager-1.36.0-11.el8_6.x86_64


How reproducible:

100%


Steps to Reproduce:

 * sudo ./bug.sh

Actual results:

Got IPv4 address in the order:

192.168.19.4/24
192.168.199.3/24
192.168.15.5/24

which is not desired

Expected results:

192.168.15.5/24
192.168.19.4/24
192.168.199.3/24

Additional info:

Comment 1 Gris Ge 2022-12-07 04:04:27 UTC
Created attachment 1930702 [details]
NetworkManager trace log

Comment 3 Gris Ge 2022-12-07 04:14:41 UTC
Issue also found on RHEL 8.4 rpm: NetworkManager-1.30.0-16.el8_4.x86_64

Comment 4 Gris Ge 2022-12-20 10:02:59 UTC
As explained in https://bugzilla.redhat.com/show_bug.cgi?id=2151428#c4

Preserving ipv4 address order for different subnet require ip address been removed and added back again, 
this will break some use case like keepalived: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1103

Closing as not a bug.


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