| 2016-11-22 03:36:56 |
Scott Moser |
bug |
|
|
added bug |
| 2016-11-22 03:37:15 |
Scott Moser |
nominated for series |
|
Ubuntu Xenial |
|
| 2016-11-22 03:41:21 |
Scott Moser |
attachment added |
|
journalctl -o short-precise after -proposed update https://bugs.launchpad.net/ubuntu/+source/gce-utils/+bug/1643751/+attachment/4781323/+files/xenial-proposed-cloud-init-journalctl-short-precise.txt |
|
| 2016-11-22 03:41:52 |
Scott Moser |
attachment added |
|
journalctl -o short-precise after first (unmodified) boot https://bugs.launchpad.net/ubuntu/+source/gce-utils/+bug/1643751/+attachment/4781324/+files/orig-boot-journalctl-short-precise.txt |
|
| 2016-11-22 03:55:06 |
Scott Moser |
description |
while testing cloud-init in -proposed for bug 1629797
I found that the changes to cloud-init create a dependency loop for
google-startup-scripts.service"
I'll attach journalctl output.
I think related is
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/311153
The change here seems to me to resolve the issue, and should be safe with new or older cloud-init as cloud-init.target is present everywhere.
$ diff -u /lib/systemd/system/google-startup-scripts.service.dist /lib/systemd/system/google-startup-scripts.service
--- /lib/systemd/system/google-startup-scripts.service.dist 2016-11-22 03:32:02.385676527 +0000
+++ /lib/systemd/system/google-startup-scripts.service 2016-11-22 03:33:31.605603761 +0000
@@ -1,9 +1,9 @@
[Unit]
Description=Google Compute Engine user startup scripts
After=local-fs.target network-online.target network.target
-After=google.service rsyslog.service cloud-final.service
+After=google.service rsyslog.service cloud-init.target
After=multi-user.target
-Wants=local-fs.target network-online.target network.target cloud-final.service
+Wants=local-fs.target network-online.target network.target
[Service]
ExecStart=/usr/share/google/run-startup-scripts |
while testing cloud-init in -proposed for bug 1629797
I found that the changes to cloud-init create a dependency loop for
google-startup-scripts.service"
I'll attach journalctl output.
I think related is
https://code.launchpad.net/~philroche/ubuntu/+source/gce-compute-image-packages/+git/gce-compute-image-packages/+merge/311153
The change here seems to me to resolve the issue, and should be safe with new or older cloud-init as cloud-init.target is present everywhere.
Summary is that we just drop 'Wants' of cloud-final.service.
I'm not sure why google-startup-scripts.service would want to make cloud-final.service start. After should be sufficient.
$ diff -u /lib/systemd/system/google-startup-scripts.service.dist /lib/systemd/system/google-startup-scripts.service
--- /lib/systemd/system/google-startup-scripts.service.dist 2016-11-22 03:32:02.385676527 +0000
+++ /lib/systemd/system/google-startup-scripts.service 2016-11-22 03:50:43.139227057 +0000
@@ -3,7 +3,7 @@
After=local-fs.target network-online.target network.target
After=google.service rsyslog.service cloud-final.service
After=multi-user.target
-Wants=local-fs.target network-online.target network.target cloud-final.service
+Wants=local-fs.target network-online.target network.target
[Service]
ExecStart=/usr/share/google/run-startup-scripts
Related bugs:
* bug 1627436: Startup scripts do not run on 1604 images |
|
| 2016-11-22 03:55:23 |
Scott Moser |
bug |
|
|
added subscriber Jon Grimm |
| 2016-11-22 04:04:08 |
Scott Moser |
bug task added |
|
gce-compute-image-packages (Ubuntu) |
|
| 2016-11-22 04:11:05 |
Scott Moser |
bug task deleted |
gce-compute-image-packages (Ubuntu) |
|
|
| 2016-11-22 04:11:15 |
Scott Moser |
gce-utils (Ubuntu): status |
New |
Confirmed |
|
| 2016-11-22 04:11:20 |
Scott Moser |
gce-utils (Ubuntu): importance |
Undecided |
High |
|
| 2016-11-22 04:34:30 |
Scott Moser |
gce-utils (Ubuntu): status |
Confirmed |
Incomplete |
|
| 2017-01-22 04:17:18 |
Launchpad Janitor |
gce-utils (Ubuntu): status |
Incomplete |
Expired |
|
