What were you trying to do that didn't work?

nm-cloud-setup.service fails/timedout with below messages:

+++

Jun 13 16:59:42 xxx systemd[1]: Started Periodically run nm-cloud-setup.
 :
Jun 13 16:59:53 xxx systemd[1]: nm-cloud-setup.service: Main process exited, code=killed, status=15/TERM
Jun 13 16:59:53 xxx systemd[1]: nm-cloud-setup.service: Failed with result 'signal'.
 :
Jun 13 16:59:54 xxx systemd[1]: nm-cloud-setup.service: Main process exited, code=killed, status=15/TERM
Jun 13 16:59:54 xxx systemd[1]: nm-cloud-setup.service: Failed with result 'signal'.
 :
Jun 13 16:59:54 xxx systemd[1]: nm-cloud-setup.service: Main process exited, code=killed, status=15/TERM
Jun 13 16:59:54 xxx systemd[1]: nm-cloud-setup.service: Failed with result 'signal'.
 :
Jun 13 16:59:55 xxx systemd[1]: nm-cloud-setup.service: Deactivated successfully.
 :
Jun 13 16:59:56 xxx systemd[1]: nm-cloud-setup.service: Deactivated successfully.
 :
Jun 13 16:59:56 xxx systemd[1]: nm-cloud-setup.service: Start request repeated too quickly.
Jun 13 16:59:56 xxx systemd[1]: nm-cloud-setup.service: Failed with result 'start-limit-hit'.
 :
Jun 13 16:59:56 xxx nm-dispatcher[1404]: Job for nm-cloud-setup.service failed.

++++

Checking further, we see that "90-nm-cloud-setup.sh" is also trying to manage the 'lo' interface and getting timedout. Later killed by systemd.

+++

Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: new request (1 scripts)
...
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: CONNECTION_DBUS_PATH=/org/freedesktop/NetworkManager/Settings/3
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: CONNECTION_EXTERNAL=1
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: CONNECTION_FILENAME=/run/NetworkManager/system-connections/lo.nmconnection
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: CONNECTION_UUID=3bfe1a6b-4d9f-4b07-b145-b37e73da287f
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: CONNECTION_ID=lo
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: DEVICE_IFACE=lo
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: DEVICE_IP_IFACE=lo
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: environment: NM_DISPATCHER_ACTION=pre-up
...
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo]: start running ordered scripts...
Jul 04 13:27:18 xxx nm-dispatcher[940]: req:3 'pre-up' [lo], "/usr/lib/NetworkManager/dispatcher.d/pre-up.d/90-nm-cloud-setup.sh": run script
...
...
jul 04 13:27:19 xxx NetworkManager[933]: <debug> [1720067239.0371] manager: startup complete is waiting for device 'lo' (activation-1)  <-----------------------
Jul 04 13:27:19 xxx systemd[1]: nm-cloud-setup.service: Main process exited, code=killed, status=15/TERM
Jul 04 13:27:19 xxx systemd[1]: nm-cloud-setup.service: Failed with result 'signal'.
Jul 04 13:27:19 xxx systemd[1]: Stopped Automatically configure NetworkManager in cloud.
Jul 04 13:27:19 xxx systemd[1]: Starting Automatically configure NetworkManager in cloud...

+++

Is this expected ?  We suggested customer to add below lines to 90-nm-cloud-setup.sh  script so that "lo" interface can be skipped and that helped in avoiding above error messages.

+++

if [ "$1" == "eth0" -a "$2" == "pre-up" ] || [ "$1" == "eth1" -a "$2" == "pre-up" ] ; then
    .....
fi

+++

Please provide the package NVR for which bug is seen:

NetworkManager-1.46.0-4.el9_4.x86_64             

NetworkManager-cloud-setup-1.46.0-4.el9_4.x86_64 
NetworkManager-libnm-1.46.0-4.el9_4.x86_64       
NetworkManager-team-1.46.0-4.el9_4.x86_64        
NetworkManager-tui-1.46.0-4.el9_4.x86_64    

How reproducible:

Always for customer.