> due to network not being fully set up when startup scripts are run. google-startup-scripts.service starts well after the network is online, so I think that the actual reason is that cc_apt_configure hasn't ran yet when the startup script starts. The diff looks like some apt mirrors configured by cloud-init, possibly via GCE's vendordata?
> This can be fixed by adding an explict `After=cloud-config.service` to the google-startup-scripts.service file, which enforces the correct ordering between google-startup-scripts and cloud-init. +1 agreed, that should fix it. However if ssh login needs to be possible (which I do not know) when the script runs, then you may want to order after systemd-user-sessions.service instead (see this bug[1] for context). That all said, the second critical chain looks unusual - what took ~16.6s between sysinit.target and multi-user.target? [1] https://bugs.launchpad.net/uvtool/+bug/2039441 -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2057965 Title: google-startup-scripts runs before cloud-init finished network setup To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/2057965/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
