[Bug 1901033] [NEW] google-startup-scripts service no longer waits for cloud-init/snapd.seeded

[Robert C Jennings]

Public bug reported:

We have a cloud-images qualification test for google startup scripts to
ensure that cloud-init customizations are available before the user
startup script is run.  That test is failing and investigation shows
that we have a functional regression from gce-compute-image-packages to
the new google-guest-agent.  Without waiting for cloud-final and
snapd.seeded we won't present a consistent system for users to run
scripts that have archive mirrors set up, GCE's google-cloud-sdk snap
installed, users in the proper groups, or other customizations owned by
those services.  We are not holding groovy release on this bug, but we
would like this treated with priority and it is a blocker for SRU.

/usr/lib/systemd/system/google-startup-scripts.service in focal from
gce-compute-image-packages:

[Unit]
Description=Google Compute Engine Startup Scripts
After=network-online.target network.target rsyslog.service
After=google-instance-setup.service google-network-daemon.service
After=cloud-final.service multi-user.target
Wants=cloud-final.service
After=snapd.seeded.service
Wants=snapd.seeded.service

/usr/lib/systemd/system/google-startup-scripts.service in groovy from
google-guest-agent:

[Unit]
Description=Google Compute Engine Startup Scripts
Wants=network-online.target rsyslog.service
After=network-online.target rsyslog.service google-guest-agent.service
Before=apt-daily.service

** Affects: google-guest-agent (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to google-guest-agent in Ubuntu.
https://bugs.launchpad.net/bugs/1901033

Title:
  google-startup-scripts service no longer waits for cloud-
  init/snapd.seeded

Status in google-guest-agent package in Ubuntu:
  New

Bug description:
  We have a cloud-images qualification test for google startup scripts
  to ensure that cloud-init customizations are available before the user
  startup script is run.  That test is failing and investigation shows
  that we have a functional regression from gce-compute-image-packages
  to the new google-guest-agent.  Without waiting for cloud-final and
  snapd.seeded we won't present a consistent system for users to run
  scripts that have archive mirrors set up, GCE's google-cloud-sdk snap
  installed, users in the proper groups, or other customizations owned
  by those services.  We are not holding groovy release on this bug, but
  we would like this treated with priority and it is a blocker for SRU.

  /usr/lib/systemd/system/google-startup-scripts.service in focal from
  gce-compute-image-packages:

  [Unit]
  Description=Google Compute Engine Startup Scripts
  After=network-online.target network.target rsyslog.service
  After=google-instance-setup.service google-network-daemon.service
  After=cloud-final.service multi-user.target
  Wants=cloud-final.service
  After=snapd.seeded.service
  Wants=snapd.seeded.service

  /usr/lib/systemd/system/google-startup-scripts.service in groovy from
  google-guest-agent:

  [Unit]
  Description=Google Compute Engine Startup Scripts
  Wants=network-online.target rsyslog.service
  After=network-online.target rsyslog.service google-guest-agent.service
  Before=apt-daily.service

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/google-guest-agent/+bug/1901033/+subscriptions