cloud-init generates runcmd and fails to execute it on first boot

Bug #1158724 reported by James Page
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
cloud-init (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

I noticed this when bootstrapping a juju raring environment on an openstack cloud using a raring image from 11/03.

cloud-init picks up the runcmd content and write it to disk but it never actually gets executed.

I removed /var/lib/cloud/instances/*, rebooted and it ran it second time round.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: cloud-init 0.7.2~bzr795-0ubuntu1
ProcVersionSignature: User Name 3.8.0-11.20-generic 3.8.2
Uname: Linux 3.8.0-11-generic x86_64
ApportVersion: 2.9.2-0ubuntu2
Architecture: amd64
Date: Fri Mar 22 11:18:35 2013
Ec2AMI: ami-00000218
Ec2AMIManifest: FIXME
Ec2AvailabilityZone: nova
Ec2InstanceType: m1.medium
Ec2Kernel: unavailable
Ec2Ramdisk: unavailable
MarkForUpload: True
PackageArchitecture: all
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)

Revision history for this message
James Page (james-page) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in cloud-init (Ubuntu):
status: New → Confirmed
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.