can't give "always" as frequency for cloud-init-run-module

Bug #568139 reported by Gabriel Nell
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Fix Released
Low
Unassigned

Bug Description

Binary package hint: cloud-init

From doing a brief code inspection it looks like the frequency "always" is meant to tell cloud-init to run this every time (eg, every boot). I expected that running the following would run the cloud scripts

cloud-init-run-module always user-scripts execute run-parts --regex '.*' /var/lib/cloud/data/scripts

The first time it does cause the scripts to be executed, but it creates the file

/var/lib/cloud/sem/user-scripts.always

And when executed again I get the message

user-scripts already ran always

Related branches

Scott Moser (smoser)
Changed in cloud-init (Ubuntu):
importance: Undecided → Low
status: New → Triaged
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package cloud-init - 0.5.12-0ubuntu1

---------------
cloud-init (0.5.12-0ubuntu1) maverick; urgency=low

  * New upstream release.
  * fix cloud-init-run-module to allow 'always' (LP: #568139)
  * add support for setting debconf selections
  * add cloud-config support for debconf selections (LP: #582667),
    byobu enablement, and ssh-import-lp-id
 -- Scott Moser <email address hidden> Fri, 18 Jun 2010 15:48:14 -0400

Changed in cloud-init (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.