I found no Ordering cycle breaks that would imply that the google-guest-agent got "unloaded" from the primary boot target objectives in journalctl.
Attached is the journalctl from a machine that was only launched and rebooted 1. After the reboot you can egrep 'GCE|gpasswd' to see the operations of google-guest-agent finally start to occur.
I found no Ordering cycle breaks that would imply that the google-guest-agent got "unloaded" from the primary boot target objectives in journalctl.
Attached is the journalctl from a machine that was only launched and rebooted 1. After the reboot you can egrep 'GCE|gpasswd' to see the operations of google-guest-agent finally start to occur.