Comment 2 for bug 1835275

I reran applying the network configuration with debug mode enabled as follows

systemctl stop systemd-networkd
SYSTEMD_LOG_LEVEL=debug /lib/systemd/systemd-networkd

While nothing in particular stood out from the debug output I did see this in journalctl -u systemd-networkd

ul 09 00:37:13 maas-test-2 systemd[1]: Started Network Service.
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: bond0: netdev could not be created: Operation not supported
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: lo: Link is not managed by us
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp1s0: Link is not managed by us
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp2s0: Link is not managed by us
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp3s0: IPv6 successfully enabled
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp2s0: Could not join netdev: No such device
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp2s0: Failed
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp1s0: Could not join netdev: No such device
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp1s0: Failed
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: Could not emit changed OperationalState: Transport endpoint is not connected
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp3s0: Gained carrier
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: Could not emit changed OperationalState: Transport endpoint is not connected
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: enp3s0: DHCPv4 address 192.168.122.241/24 via 192.168.122.1
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: Not connected to system bus, not setting hostname.
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: Could not emit changed OperationalState: Transport endpoint is not connected
Jul 09 00:37:14 maas-test-2 systemd-networkd[1734]: enp3s0: Gained IPv6LL
Jul 09 00:37:14 maas-test-2 systemd-networkd[1734]: enp3s0: Configured