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:

It has been observed that when applying NNCP that defines only global DNS config and does not configure any interface specifically, the IP addresses on the interface holding default gateway get reordered.

This is not desired for various reasons, but to simplify it can be said that global DNS config should not affect at all the IP configuration of the interface.

Version-Release number of selected component (if applicable):

nmstate-1.0.2-21.el8_4


How reproducible:

Always, if order of IP addresses before applying NNCP is not an alphabetical order.


Steps to Reproduce:
1. Create network interface with multiple IP addresses
2. Make sure the order of IP addresses is not alphabetical
3. Create NNCP without IP address configuration (e.g. with only global DNS configuration)

Actual results:

IP addresses on the interface holding default gateway are now sorted alphabetically. The 1st IP address from before NNCP is not any more the 1st.


Expected results:

Order of IP addresses remain unchanged.

Please note this affects a customer with OCP 4.10, thus it needs a backport back to 8.4

Patch merged in upstream: https://github.com/nmstate/nmstate/pull/2274

Created attachment 1963090 [details]
verified.log

Verified with:
nmstate-1.4.4-2.el8.x86_64
nispor-1.2.10-1.el8.x86_64
NetworkManager-1.40.16-4.el8.x86_64
DISTRO=RHEL-8.9.0-20230503.20

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 (nmstate 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-2023:6918