[Bug 1427999] Re: cloud-init does not purge with systemd

[Martin Pitt]

Ah, I know now. cloud-init's prerm stops cloud-init-local.service, so if
you are trying to purge cloud-init from user-data, stopping this will
kill apt/dpkg/etc. I'll work around that in autopkgtest, but I wonder if
we want to support that case in cloud-init itself. I'll have a closer
look and prepare a patch.

** Summary changed:

- cloud-init does not purge with systemd
+ purging cloud-init from user-data commands does not work under systemd

** Changed in: cloud-init (Ubuntu)
   Importance: Medium => Low

** Changed in: cloud-init (Ubuntu)
     Assignee: (unassigned) => Martin Pitt (pitti)

** Also affects: autopkgtest (Ubuntu)
   Importance: Undecided
       Status: New

** Changed in: autopkgtest (Ubuntu)
       Status: New => In Progress

** Changed in: autopkgtest (Ubuntu)
   Importance: Undecided => High

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

Title:
  purging cloud-init from user-data commands does not work under systemd

Status in autopkgtest package in Ubuntu:
  In Progress
Status in cloud-init package in Ubuntu:
  New

Bug description:
  Apparently yesterday the cloud images at http://cloud-
  images.ubuntu.com/vivid/ were switched to boot with systemd, with
  init=/lib/systemd/systemd . 20150303/ still worked (with upstart),
  20150304/ hangs:

  [   15.009125] cloud-init[541]: Cloud-init v. 0.7.7 running 'init-local' at Wed, 04 Mar 2015 07:31:54 +0000. Up 13.71 seconds.
  [  OK  ] Started Initial cloud-init job (pre-networking).
           Starting Initial cloud-init job (metadata service crawler)...
  [   15.471963] cloud-init[747]: Cloud-init v. 0.7.7 running 'init' cron.service
  [...]
  [   15.824259] cloud-init[781]: Cloud-init v. 0.7.7 running 'modules:config' at Wed, 04 Mar 2015 07:31:56 +0000. Up 15.73 seconds.
  [   15.824463] cloud-init[781]: 2015-03-04 07:31:56,991 - cc_emit_upstart.py[WARNING]: Emission of upstart event cloud-config failed due to: Unexpected error while running command.
  [   15.824589] cloud-init[781]: Command: ['initctl', 'emit', 'cloud-config', 'CLOUD_CFG=/var/lib/cloud/instance/cloud-config.txt']
  [   15.824698] cloud-init[781]: Exit code: 1
  [   15.824802] cloud-init[781]: Reason: -
  [   15.824903] cloud-init[781]: Stdout: ''
  [   15.825003] cloud-init[781]: Stderr: 'initctl: Unable to connect to Upstart: Failed to connect to socket /com/ubuntu/upstart: Connection refused\n'
  [   16.003444] cloud-init[781]: Generating locales...
  [   16.036106] cloud-init[781]: en_US.UTF-8... up-to-date
  [   16.040818] cloud-init[781]: Generation complete.
           Stopping OpenBSD Secure Shell server...
  [  OK  ] Stopped OpenBSD Secure Shell server.
  [  OK  ] Sta

  and there it hangs. When trying to boot, it tries to talk to
  169.254.169.254 which times out.

  The initctl emit failure looks related, this obviously won't work
  under systemd. This probably needs to be replaced with some "systemctl
  start ..." equivalent? Note that you can test for systemd with [ -d
  /run/systemd/system ], that's the canonical test.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/autopkgtest/+bug/1427999/+subscriptions