Activity log for bug #613309

Date Who What changed Old value New value Message
2010-08-04 05:37:20 Pete Crossley bug added bug
2010-08-04 05:45:54 Pete Crossley attachment added This is the upstart scripts that I had to use to make this functional. http://launchpadlibrarian.net/53029398/cloud-init.patch
2010-08-04 15:55:27 Pete Crossley bug added subscriber Martin Pitt
2010-08-04 15:56:28 Pete Crossley description Binary package hint: cloud-init All lucid/maverick source packages, The following upstart scripts need to wait for the 'cloud-config' status in addition to what they currently wait for, otherwise userdata might not be loaded yet. cloud-apt-update-upgrade.conf cloud-config-misc.conf cloud-config-mounts.conf cloud-config-ssh.conf cloud-disable-ec2-metadata.conf cloud-ec2-ebs-mounts.conf cloud-raid.conf cloud-runurl.conf ~~ most of these need to just add 'and cloud-init' but one or two need to just 'start on cloud-init' ~~~ cloud-run-user-script.conf needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config-misc)' We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature. Binary package hint: cloud-init All lucid/maverick source packages, The following upstart scripts need to wait for the 'cloud-config' status in addition to what they currently wait for, otherwise userdata might not be loaded yet. cloud-apt-update-upgrade.conf cloud-config-misc.conf cloud-config-mounts.conf cloud-config-ssh.conf cloud-disable-ec2-metadata.conf cloud-ec2-ebs-mounts.conf cloud-raid.conf cloud-runurl.conf ~~ most of these need to just add 'and cloud-config' but one or two need to just 'start on cloud-config' ~~~ cloud-run-user-script.conf needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config-misc)' We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature.
2010-08-04 15:59:50 Martin Pitt removed subscriber Martin Pitt
2010-08-04 16:00:16 Martin Pitt bug added subscriber Ubuntu Stable Release Updates Team
2010-08-04 16:00:30 Martin Pitt bug added subscriber Ubuntu Server Team
2010-08-04 16:00:36 Martin Pitt removed subscriber Ubuntu Stable Release Updates Team
2010-08-04 16:30:40 Brian Murray bug added subscriber Ubuntu Review Team
2010-08-04 16:30:43 Brian Murray tags ec2 uec upstart userdata ec2 patch uec upstart userdata
2010-08-05 19:05:57 Scott Moser bug added subscriber Scott Moser
2010-08-08 05:34:21 Pete Crossley summary upstart scripts do not wait for 'cloud-config' status cloud-run-user-script.conf upstart script needs to run after all other cloud-init processes
2010-08-08 05:35:49 Pete Crossley attachment removed This is the upstart scripts that I had to use to make this functional. http://launchpadlibrarian.net/53029398/cloud-init.patch
2010-08-09 15:20:42 Launchpad Janitor branch linked lp:~smoser/ubuntu/lucid/cloud-init/bug613309
2010-08-09 15:27:23 Scott Moser nominated for series Ubuntu Lucid
2010-08-09 15:27:23 Scott Moser bug task added cloud-init (Ubuntu Lucid)
2010-08-09 15:29:28 Scott Moser cloud-init (Ubuntu): importance Undecided Medium
2010-08-09 15:29:28 Scott Moser cloud-init (Ubuntu): status New Fix Released
2010-08-09 21:33:52 Scott Moser description Binary package hint: cloud-init All lucid/maverick source packages, The following upstart scripts need to wait for the 'cloud-config' status in addition to what they currently wait for, otherwise userdata might not be loaded yet. cloud-apt-update-upgrade.conf cloud-config-misc.conf cloud-config-mounts.conf cloud-config-ssh.conf cloud-disable-ec2-metadata.conf cloud-ec2-ebs-mounts.conf cloud-raid.conf cloud-runurl.conf ~~ most of these need to just add 'and cloud-config' but one or two need to just 'start on cloud-config' ~~~ cloud-run-user-script.conf needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config-misc)' We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature. Binary package hint: cloud-init All lucid/maverick source packages, The following upstart scripts need to wait for the 'cloud-config' status in addition to what they currently wait for, otherwise userdata might not be loaded yet. cloud-apt-update-upgrade.conf cloud-config-misc.conf cloud-config-mounts.conf cloud-config-ssh.conf cloud-disable-ec2-metadata.conf cloud-ec2-ebs-mounts.conf cloud-raid.conf cloud-runurl.conf ~~ most of these need to just add 'and cloud-config' but one or two need to just 'start on cloud-config' ~~~ cloud-run-user-script.conf needs 'start on (stopped rc RUNLEVEL=[2345] and stopped cloud-config-misc)' We need this package to work in ec2 as well as UEC otherwise it make provisioning of a new instance much harder and defeats the purpose of this package. Since Lucid is LTS I would like to see a SRU for this issue as well since it prevent out of the box/repo use of this feature. ==== Begin SRU Justification ==== Impact: The impact of this bug is that a popular portion of "cloud-config" syntax [1] is not easily used in the 10.04 images. If the user specifies commands to run, they cannot rely on other portions of cloud-init having finished before those scripts run. The big examples is that if the user installs a package via 'pkgs', they cannot rely on it being present in their 'runcmd'. The ordering is simply not guaranteed. Solution: The solution is to make the upstart script that executes the user's commands depend on 'stopped' of each of the other upstart jobs. In this manner, it will not execute until the other jobs are finished. Patch: Available in branch attached to this bug [2] Regression Potential: There should be low potential for regression and low realistic change of user expectations. Previously, the order was non-deterministic, this will guarantee that jobs run after packages are installed. TEST Case: * launch ec2 instance (ubuntu-lucid-10.04-i386-server-20100427.1, such as ami-fd4aa494) with user data having 'packages' and 'runcmd' section. Such as: | #cloud-config | packages: [ bzr, ubuntu-dev-tools, ccache, vim-nox, git-core, lftp ] | runcmd: | - [ sudo, -Hu, ubuntu, sh, -c 'bzr branch lp:ubuntu/lucid-proposed/cloud-init 2>&1 | tee cmd.log' ] * without a fix for this bug, the ordering is indeterminable, but most likely, the 'bzr branch' command will run before bzr is installed. With the fix, it is guaranteed to run afterwards. -- [1] http://bazaar.launchpad.net/~ubuntu-branches/ubuntu/lucid/cloud-init/lucid-proposed/annotate/head%3A/doc/examples/cloud-config.txt [2] http://bazaar.launchpad.net/~smoser/ubuntu/lucid/cloud-init/bug613309/revision/17 ==== End SRU Justification =====
2010-08-11 15:54:28 Scott Moser bug added subscriber Ubuntu Stable Release Updates Team
2010-08-11 19:02:31 Scott Moser cloud-init (Ubuntu Lucid): importance Undecided High
2010-08-11 19:02:31 Scott Moser cloud-init (Ubuntu Lucid): status New In Progress
2010-08-11 19:02:31 Scott Moser cloud-init (Ubuntu Lucid): milestone lucid-updates
2010-08-17 13:00:42 Launchpad Janitor branch linked lp:ubuntu/lucid-proposed/cloud-init
2010-08-18 14:35:47 Martin Pitt cloud-init (Ubuntu Lucid): status In Progress Fix Committed
2010-08-18 14:35:53 Martin Pitt bug added subscriber SRU Verification
2010-08-18 14:35:58 Martin Pitt tags ec2 patch uec upstart userdata ec2 patch uec upstart userdata verification-needed
2010-08-19 19:16:51 Scott Moser tags ec2 patch uec upstart userdata verification-needed ec2-images patch uec-images upstart verification-done
2010-08-24 09:05:53 Launchpad Janitor cloud-init (Ubuntu Lucid): status Fix Committed Fix Released
2010-08-24 12:57:24 Launchpad Janitor branch linked lp:ubuntu/lucid-updates/cloud-init