[Bug 1103881] Re: cloud-final is never executed if upstart is upgraded during initialization of the image

Scott Moser smoser at ubuntu.com
Thu Feb 14 17:48:11 UTC 2013


To reproduce outside of "cloud", you can basically follow the blog post
that I've got at [1].

Using this user-data to make sure you can login:
#cloud-config-archive
- content: |
   #!/bin/sh
   echo "==== $(date -R): user-script run ===" | tee /run/user-script.log
- filename: myjob.conf
  content: |
   #upstart-job
   description "a test upstart job"
   start on stopped rc RUNLEVEL=[2345]
   console output
   task
   script
   echo "==== $(date -R): upstart job run ===" | tee /run/upstart-job.log
   end script
- content: |
   #cloud-config
   password: passw0rd
   chpasswd: { expire: False }
   ssh_pwauth: True


Then:
sudo apt-get install kvm cloud-utils genisoimage
wget http://cloud-images.ubuntu.com/raring/current/raring-server-cloudimg-amd64-disk1.img -O disk.img.dist
qemu-img convert -O qcow2 disk.img.dist disk.img.orig

qemu-img create -f qcow2 -b disk.img.orig disk.img
cloud-localds my-seed.img my-user-data
kvm -net nic -net user,hostfwd=tcp::2222-:22 \
   -hda disk.img -hdb my-seed.img -m 512

Due to the fact that the bug blocks gettys from running, you'll have to ssh in.
Thats why i've done the host forwarding there.
You'll be able to log in with 'ubuntu' and 'passw0rd'.  Remember that console output will be going to the serial device.

--
[1] http://ubuntu-smoser.blogspot.com/2013/02/using-ubuntu-cloud-images-without-cloud.html

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

Title:
  cloud-final is never executed if upstart is upgraded during
  initialization of the image

Status in “cloud-init” package in Ubuntu:
  Confirmed
Status in “upstart” package in Ubuntu:
  Confirmed

Bug description:
  During a cloud image initialization, the service cloud-final is never
  executed if the cloud-config script contains an "upgrade" directive
  and upstart is part of the upgraded packages:

  TESTCASE:
  1. Download a cloud image from http://cloud-images.ubuntu.com/raring/ with an outdated version of upstart (e.g 2013.01.23 - I saved this image, if you need it and it is not available from the mirror just ask)
  2. Prepare a cloud-config script with the directives (example cloud-config script used by lp:auto-package-testing attached):

  apt_update: true
  apt_upgrade: true

  3. Initialize the cloud image with this cloud-config script

  EXPECTED RESULT:
  Installation finish

  ACTUAL RESULT
  The service cloud-final is never executed and the flag boot-finished is not present.

  cloud-init logs of a failed installation attached.

  Related bugs:
   * bug 1080841: should reload configuration if an upstart job is added
   * bug 1124384: reload-configuration can confuse upstart

  ProblemType: Bug
  DistroRelease: Ubuntu 13.04
  Package: cloud-init (not installed)
  ProcVersionSignature: Ubuntu 3.8.0-1.5-generic 3.8.0-rc4
  Uname: Linux 3.8.0-1-generic x86_64
  ApportVersion: 2.8-0ubuntu2
  Architecture: amd64
  Date: Thu Jan 24 09:08:19 2013
  MarkForUpload: True
  ProcEnviron:
   TERM=xterm
   PATH=(custom, no user)
   XDG_RUNTIME_DIR=<set>
   LANG=en_US.UTF-8
   SHELL=/bin/bash
  SourcePackage: cloud-init
  UpgradeStatus: Upgraded to raring on 2012-01-31 (358 days ago)

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1103881/+subscriptions




More information about the foundations-bugs mailing list