Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2139443

Summary: Preserve the order of IPv6 addresses
Product: Red Hat Enterprise Linux 8 Reporter: Gris Ge <fge>
Component: NetworkManagerAssignee: NetworkManager Development Team <nm-team>
Status: CLOSED NOTABUG QA Contact: Desktop QE <desktop-qa-list>
Severity: medium Docs Contact:
Priority: medium    
Version: 8.7CC: bgalvani, lrintel, rkhan, sukulkar, thaller, till
Target Milestone: rcFlags: pm-rhel: mirror+
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-11-02 14:35:40 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:

Description Gris Ge 2022-11-02 14:30:16 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
NetworkManager-1.40.0-1.el8.x86_64

How reproducible:
100%

Steps to Reproduce:

nmcli c del dummy1

nmcli c add type dummy ifname dummy1 \
    connection.id dummy1 \
    ipv4.method manual \
    ipv4.address 192.0.2.2/24,192.0.2.1/24 \
    ipv6.method manual \
    ipv6.address 2001:db8:2::1/64,2001:db8:1::1/64

sleep 2
ip addr show dev dummy1

Actual results:

2001:db8:2::1/64 been listed after 2001:db8:1::1/64

Expected results:

2001:db8:2::1/64 been listed before 2001:db8:1::1/64


Additional info:
Comment 1 Thomas Haller 2022-11-02 14:34:52 UTC 
in the past, the order of "ipv6.addresses" was reversed.

This was fixed/changed upstream in 1.40.0 and in rhel-9.1+.

rhel-8.7+ keeps the old behavior.

This is intended.

See this downstream patch: https://gitlab.com/redhat/centos-stream/rpms/NetworkManager/-/blob/53768ceaad3618e01be7597075405a05914193cf/0003-order-ipv6-addresses.patch



The point is to stick to earlier rhel-8 behavior, which makes it inconsistent with upstream and rhel-9.



This cannot be fixed, without breaking something else.