| 2020-10-22 14:02:44 |
Robert C Jennings |
bug |
|
|
added bug |
| 2020-10-22 14:02:55 |
Robert C Jennings |
bug |
|
|
added subscriber Balint Reczey |
| 2020-10-22 14:03:27 |
Robert C Jennings |
bug |
|
|
added subscriber Liam Hopkins |
| 2020-10-22 14:03:38 |
Robert C Jennings |
bug |
|
|
added subscriber Zach Marano |
| 2020-10-22 14:21:18 |
Robert C Jennings |
bug watch added |
|
https://github.com/GoogleCloudPlatform/guest-agent/issues/84 |
|
| 2020-10-22 14:21:18 |
Robert C Jennings |
bug task added |
|
google-guest-agent |
|
| 2020-10-22 14:59:57 |
Robert C Jennings |
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 |
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
===
Workaround:
As a work-around users can add cloud-init status --wait to the beginning of their startup script (as cloud-init does wait for snap seeding to complete). |
|
| 2020-10-22 15:02:03 |
Balint Reczey |
google-guest-agent (Ubuntu): assignee |
|
Balint Reczey (rbalint) |
|
| 2020-10-22 16:49:46 |
Balint Reczey |
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
===
Workaround:
As a work-around users can add cloud-init status --wait to the beginning of their startup script (as cloud-init does wait for snap seeding to complete). |
[Impact]
* 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.
[Test Case]
* Observe google-startup-scripts waiting for snapd.seeded and cloud-final:
root@rbalint-gg-1:~# systemd-analyze dot| egrep 'google-startup-scripts.*(snapd\.seeded|cloud-final)'
"google-startup-scripts.service"->"snapd.seeded.service" [color="green"];
"google-startup-scripts.service"->"cloud-final.service" [color="green"];
"google-startup-scripts.service"->"cloud-final.service" [color="grey66"];
"google-startup-scripts.service"->"snapd.seeded.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
[Regression Potential]
* The fix is adding missing dependencies for the services shipped in google-guest-agent. The same dependencies were added when gce-compute-image-packages shipped those services thus restoring them would cause issues, but in theory the added dependencies could introduce cycles making the service ordering unreliable. I have not seen any sign of such issue.
[Original Bug Text]
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 |
|
| 2020-10-22 17:56:16 |
Balint Reczey |
description |
[Impact]
* 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.
[Test Case]
* Observe google-startup-scripts waiting for snapd.seeded and cloud-final:
root@rbalint-gg-1:~# systemd-analyze dot| egrep 'google-startup-scripts.*(snapd\.seeded|cloud-final)'
"google-startup-scripts.service"->"snapd.seeded.service" [color="green"];
"google-startup-scripts.service"->"cloud-final.service" [color="green"];
"google-startup-scripts.service"->"cloud-final.service" [color="grey66"];
"google-startup-scripts.service"->"snapd.seeded.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
[Regression Potential]
* The fix is adding missing dependencies for the services shipped in google-guest-agent. The same dependencies were added when gce-compute-image-packages shipped those services thus restoring them would cause issues, but in theory the added dependencies could introduce cycles making the service ordering unreliable. I have not seen any sign of such issue.
[Original Bug Text]
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 |
[Impact]
* 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.
[Test Case]
* Observe google-startup-scripts waiting for snapd.seeded and cloud-final:
root@rbalint-gg-1:~# systemd-analyze dot| egrep 'google-startup-scripts.*(snapd\.seeded|cloud-final)'
"google-startup-scripts.service"->"snapd.seeded.service" [color="green"];
"google-startup-scripts.service"->"cloud-final.service" [color="green"];
"google-startup-scripts.service"->"cloud-final.service" [color="grey66"];
"google-startup-scripts.service"->"snapd.seeded.service" [color="grey66"];
Color legend: black = Requires
dark blue = Requisite
dark grey = Wants
red = Conflicts
green = After
[Regression Potential]
* The fix is adding missing dependencies for the services shipped in google-guest-agent. The same dependencies were added when gce-compute-image-packages shipped those services thus restoring them would cause issues, but in theory the added dependencies could introduce cycles making the service ordering unreliable. I have not seen any sign of such issue.
[Original Bug Text]
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
===
Workaround:
As a work-around users can add cloud-init status --wait to the beginning of their startup script (as cloud-init does wait for snap seeding to complete). |
|
| 2020-10-23 14:12:57 |
Timo Aaltonen |
google-guest-agent (Ubuntu Groovy): status |
New |
Fix Committed |
|
| 2020-10-23 14:13:00 |
Timo Aaltonen |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-10-23 14:13:02 |
Timo Aaltonen |
bug |
|
|
added subscriber SRU Verification |
| 2020-10-23 14:13:10 |
Timo Aaltonen |
tags |
|
verification-needed verification-needed-groovy |
|
| 2020-10-26 11:06:56 |
Balint Reczey |
tags |
verification-needed verification-needed-groovy |
verification-done verification-done-groovy |
|
| 2020-10-26 11:08:06 |
Balint Reczey |
google-guest-agent (Ubuntu Groovy): importance |
Undecided |
High |
|
| 2020-10-26 11:08:12 |
Balint Reczey |
google-guest-agent (Ubuntu): importance |
Undecided |
High |
|
| 2020-11-02 08:34:43 |
Launchpad Janitor |
google-guest-agent (Ubuntu): status |
New |
Fix Released |
|
| 2020-11-02 14:44:39 |
Launchpad Janitor |
google-guest-agent (Ubuntu Groovy): status |
Fix Committed |
Fix Released |
|
| 2020-11-02 14:44:42 |
Łukasz Zemczak |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-04-20 06:54:07 |
Bug Watch Updater |
google-guest-agent: status |
Unknown |
New |
|
