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 2082000 - The primary ip address will be changed after assigning multiple secondary ip addresses from the web console in Alibaba Cloud [rhel-8.7]
Summary: The primary ip address will be changed after assigning multiple secondary ip ...
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
unspecified
medium
Target Milestone: rc
: ---
Assignee: Thomas Haller
QA Contact: Vladimir Benes
Mayur Patil
URL:
Whiteboard:
Depends On: 2079849
Blocks: 2097604
TreeView+ depends on / blocked
 
Reported: 2022-05-05 07:45 UTC by Thomas Haller
Modified: 2022-11-08 11:23 UTC (History)
18 users (show)

Fixed In Version: NetworkManager-1.39.5-1.el8
Doc Type: Bug Fix
Doc Text:
.An instance now retains the primary IP address even after starting the nm-cloud-setup service in Alibaba Cloud Previously, after launching an instance in the Alibaba Cloud, the nm-cloud-setup service configured the incorrect IP address as the primary IP address in case of multiple IPv4 addresses. Consequently, this affected the selection of the IPv4 source address for outgoing connections. With this update, after configuring secondary IP addresses manually, the NetworkManager package fetches the primary IP address from primary-ip-address metadata and configures both primary and secondary IP addresses correctly.
Clone Of: 2079849
: 2097604 (view as bug list)
Environment:
Last Closed: 2022-11-08 10:10:31 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-121710 0 None None None 2022-05-11 11:18:53 UTC
Red Hat Product Errata RHBA-2022:7680 0 None None None 2022-11-08 10:10:55 UTC

Description Thomas Haller 2022-05-05 07:45:47 UTC 
+++ This bug was initially created as a clone of Bug #2079849 +++

nm-cloud-setup has a problem on Alibaba Cloud that it might not configure the primary address as primary.

Fixed upstream (https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/merge_requests/1201).


See details at rhel-9 bug 2079849.
Comment 2 YongkuiGuo 2022-05-18 07:57:54 UTC 
Hi Thomas,

Could you please reset the DTM? Thanks.
Comment 5 YongkuiGuo 2022-05-25 09:17:08 UTC 
Verified with NetworkManager-1.39.5-1.el8.x86_64:


Steps:


1. Create an instance with RHEL-8.7.0-20220524.0 guest image in Alibaba Cloud

2. Install the NetworkManger-cloud-setup package and edit the nm-cloud-setup service
# systemctl edit nm-cloud-setup.service
[Service]
Environment=NM_CLOUD_SETUP_ALIYUN=yes

3. 
# systemctl daemon-reload 

4. Check the primary ip address
# ip addr
...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:3e:34:dd:54 brd ff:ff:ff:ff:ff:ff
    inet 172.17.96.115/20 brd 172.17.111.255 scope global dynamic noprefixroute eth0
       valid_lft 315359615sec preferred_lft 315359615sec
    inet6 fe80::216:3eff:fe34:dd54/64 scope link 
       valid_lft forever preferred_lft forever

The primary ip is '172.17.96.115'.

5. Assign three secondary ip addresses to the instance from the web console and check all the ip addresses from meta-data
# curl http://100.100.100.200/2016-01-01/meta-data/network/interfaces/macs/00:16:3e:34:dd:54/private-ipv4s
["172.17.96.118","172.17.96.117","172.17.96.116","172.17.96.115"]

6. Start the nm-cloud-setup service
# systemctl start nm-cloud-setup.service

7. Check the ip addresses again
# ip addr
...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:3e:34:dd:54 brd ff:ff:ff:ff:ff:ff
    inet 172.17.96.115/20 brd 172.17.111.255 scope global noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet 172.17.96.118/20 brd 172.17.111.255 scope global secondary noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet 172.17.96.117/20 brd 172.17.111.255 scope global secondary noprefixroute eth0
       valid_lft forever preferred_lft forever
    inet 172.17.96.116/20 brd 172.17.111.255 scope global secondary noprefixroute eth0
       valid_lft forever preferred_lft forever

The primary ip is still '172.17.96.115', and all the secondary ip addresses have been configured correctly.

8. Unassign all the secondary ip addresses and check the ip addresses from meta-data
# curl http://100.100.100.200/2016-01-01/meta-data/network/interfaces/macs/00:16:3e:34:dd:54/private-ipv4s
["172.17.96.115"]

9. Start the nm-cloud-setup service
# systemctl start nm-cloud-setup.service

10. Check the ip addresses again
# ip addr
...
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state UP group default qlen 1000
    link/ether 00:16:3e:34:dd:54 brd ff:ff:ff:ff:ff:ff
    inet 172.17.96.115/20 brd 172.17.111.255 scope global dynamic noprefixroute eth0
       valid_lft 315359992sec preferred_lft 315359992sec

All the configurations of the secondary ip addresses have been removed.

11. Enable and start nm-cloud-setup service and nm-cloud-setup timer
# systemctl enable --now nm-cloud-setup.service
# systemctl enable --now nm-cloud-setup.timer

12. Retest steps 5 and 8, the secondary ip addresses can be configured automatically.
Comment 6 YongkuiGuo 2022-06-13 11:15:56 UTC 
Hi sfaye,

Is this bug not qualified for z-stream? The nm-cloud-setup service should be supported from RHEL8.5 on Alibaba Cloud according to this bug: https://bugzilla.redhat.com/show_bug.cgi?id=1823315.
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.