After looking some more into this, I noticed two more things that are off:
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: bond0: netdev could not be created: Operation not supported
^ Operation not supported here is quite weird. I can't think of a reason why it could happen. Are you using a special kernel there? Is it missing some module that needs to be modprobed (bonding)? What else might make creating a bond UNSUPP?
Also, the other errors:
Jul 09 00:37:13 maas-test-2 systemd-networkd[1734]: Could not emit changed OperationalState: Transport endpoint is not connected
Indicate there is no valid connection to the systemd bus. Why would DBUS not be running? This isn't a question of mountpoints, but at the very least a question of the makeup of the ephemeral environment, for instance, if not all the services are started correctly there.
If you're in the ephemeral environment, what happens if you run:
After looking some more into this, I noticed two more things that are off:
Jul 09 00:37:13 maas-test-2 systemd- networkd[ 1734]: bond0: netdev could not be created: Operation not supported
^ Operation not supported here is quite weird. I can't think of a reason why it could happen. Are you using a special kernel there? Is it missing some module that needs to be modprobed (bonding)? What else might make creating a bond UNSUPP?
Also, the other errors:
Jul 09 00:37:13 maas-test-2 systemd- networkd[ 1734]: Could not emit changed OperationalState: Transport endpoint is not connected
Indicate there is no valid connection to the systemd bus. Why would DBUS not be running? This isn't a question of mountpoints, but at the very least a question of the makeup of the ephemeral environment, for instance, if not all the services are started correctly there.
If you're in the ephemeral environment, what happens if you run:
systemctl is-system-running
and
sudo systemd-analyze critical-chain