Hide Forgot
+++ 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.
Hi Thomas, Could you please reset the DTM? Thanks.
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.
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.
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