Bug 2178640

Summary: NNCP with DNS-only configuration reorders IP addresses
Product: Red Hat Enterprise Linux 8 Reporter: Mat Kowalski <mko>
Component: nmstateAssignee: Gris Ge <fge>
Status: CLOSED ERRATA QA Contact: Mingyu Shi <mshi>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 8.4CC: ferferna, fge, jiji, jishi, network-qe, sfaye, sgurnale, till
Target Milestone: rcKeywords: Triaged
Target Release: ---Flags: sgurnale: needinfo-
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: nmstate-1.4.3-1.el8 Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-11-14 15:26:03 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:
Attachments:
Description Flags
verified.log none

Description Mat Kowalski 2023-03-15 13:56:55 UTC 
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.
Comment 1 Mat Kowalski 2023-03-15 14:39:31 UTC 
Please note this affects a customer with OCP 4.10, thus it needs a backport back to 8.4
Comment 2 Gris Ge 2023-03-26 02:45:53 UTC 
Patch merged in upstream: https://github.com/nmstate/nmstate/pull/2274
Comment 10 Mingyu Shi 2023-05-08 02:44:14 UTC 
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
Comment 12 errata-xmlrpc 2023-11-14 15:26:03 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 (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