Error: Connection activation failed: IP configuration could not be reserved

I am provisioning RHEL 9 machines via an Ansible playbook that contains this task: - name: Set DNS server community.general.nmcli: conn_name: "{{ conn_name | default('ens192') }}" type: "{{ connection_type | default('ethernet') }}" dns4: - "{{ dns_1_ip }}" - "{{ dns_2_ip }}" state: present Up to RHEL 9.3 this playbook worked well. However, on a new RHEL 9.6 server (that I shall call myhost) Ansible returns the error > Error: Connection activation failed: IP configuration could not be reserved (no available address, timeout, etc.) On the server, the command journalctl -xe NM_CONNECTION=c337c0ba-ab72-4510-9015-2c42caccb9b5 + NM_DEVICE=ens192 returns: Jun 17 15:03:33 myhost NetworkManager: [1750165413.4029] device (ens192): disconnecting for new activation request. Jun 17 15:03:33 myhost NetworkManager: [1750165413.4029] device (ens192): state change: activated -> deactivating (reason 'new-activation', managed-type: 'full') Jun 17 15:03:33 myhost NetworkManager: [1750165413.4376] device (ens192): state change: deactivating -> disconnected (reason 'new-activation', managed-type: 'full') Jun 17 15:03:33 myhost NetworkManager: [1750165413.4494] device (ens192): Activation: starting connection 'ens192' (c337c0ba-ab72-4510-9015-2c42caccb9b5) Jun 17 15:03:33 myhost NetworkManager: [1750165413.4510] device (ens192): state change: disconnected -> prepare (reason 'none', managed-type: 'full') Jun 17 15:03:33 myhost NetworkManager: [1750165413.4513] device (ens192): state change: prepare -> config (reason 'none', managed-type: 'full') Jun 17 15:03:33 myhost NetworkManager: [1750165413.4785] device (ens192): state change: config -> ip-config (reason 'none', managed-type: 'full') Jun 17 15:03:33 myhost NetworkManager: [1750165413.4809] dhcp4 (ens192): activation: beginning transaction (timeout in 45 seconds) Jun 17 15:04:19 myhost NetworkManager: [1750165459.1052] device (ens192): state change: ip-config -> failed (reason 'ip-config-unavailable', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1065] device (ens192): Activation: failed for connection 'ens192' Jun 17 15:04:19 myhost NetworkManager: [1750165459.1068] device (ens192): state change: failed -> disconnected (reason 'none', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1159] dhcp4 (ens192): canceled DHCP transaction Jun 17 15:04:19 myhost NetworkManager: [1750165459.1160] dhcp4 (ens192): activation: beginning transaction (timeout in 45 seconds) Jun 17 15:04:19 myhost NetworkManager: [1750165459.1160] dhcp4 (ens192): state changed no lease Jun 17 15:04:19 myhost NetworkManager: [1750165459.1252] device (ens192): Activation: starting connection 'VMware customization ens192' (fdc16ed3-da99-41e1-9938-cdbb2c82f1dd) Jun 17 15:04:19 myhost NetworkManager: [1750165459.1254] device (ens192): state change: disconnected -> prepare (reason 'none', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1269] device (ens192): state change: prepare -> config (reason 'none', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1451] device (ens192): state change: config -> ip-config (reason 'none', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1511] device (ens192): state change: ip-config -> ip-check (reason 'none', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1761] device (ens192): state change: ip-check -> secondaries (reason 'none', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1762] device (ens192): state change: secondaries -> activated (reason 'none', managed-type: 'full') Jun 17 15:04:19 myhost NetworkManager: [1750165459.1766] device (ens192): Activation: successful, device activated. The server's IP address is set statically (no DHCP). The command ip addr returns: 1: lo: mtu 65536 qdisc noqueue state UNKNOWN group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 inet 127.0.0.1/8 scope host lo valid_lft forever preferred_lft forever inet6 ::1/128 scope host valid_lft forever preferred_lft forever 2: ens192: mtu 1500 qdisc mq state UP group default qlen 1000 link/ether 00:50:56:a3:26:a3 brd ff:ff:ff:ff:ff:ff altname enp11s0 inet 10.140.33.51/24 brd 10.140.33.255 scope global noprefixroute ens192 valid_lft forever preferred_lft forever inet6 fe80::250:56ff:fea3:26a3/64 scope link noprefixroute valid_lft forever preferred_lft forever Output of nmcli connection show: NAME UUID TYPE DEVICE VMware customization ens192 fdc16ed3-da99-41e1-9938-cdbb2c82f1dd ethernet ens192 lo 20226404-dda1-4e98-8bcd-3cc922f7decb loopback lo ens192 c337c0ba-ab72-4510-9015-2c42caccb9b5 ethernet -- What can I further research to troubleshoot why this Ansible playbook fails?