cloud-init fails to install juju agent after bootstrap

[ZhengPeng Hou]

output of cloud-init
http://paste.ubuntu.com/5672490/

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: cloud-init 0.7.2~bzr804-0ubuntu1
ProcVersionSignature: User Name 3.8.0-12.21-generic 3.8.2
Uname: Linux 3.8.0-12-generic x86_64
ApportVersion: 2.9.2-0ubuntu5
Architecture: amd64
Date: Wed Apr 3 03:26:10 2013
Ec2AMI: ami-1e831d77
Ec2AMIManifest: (unknown)
Ec2AvailabilityZone: us-east-1c
Ec2InstanceType: m1.small
Ec2Kernel: aki-88aa75e1
Ec2Ramdisk: unavailable
MarkForUpload: True
PackageArchitecture: all
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: cloud-init
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Scott Moser (smoser)]

could you please attach /var/log/cloud-init.log and output of 'ec2metadata --userdata' on the instance that has had the problem.

also, is this 100% reproducible?

[Scott Moser (smoser)]

and also, it looks like not all of cloud-init-output.log was pastebinned.

[ZhengPeng Hou (zhengpeng-hou)]

Not sure if its 100% reproducible, but I tried 2 times, failed 2 times, I
can give it more tries.

On Wed, Apr 3, 2013 at 8:36 PM, Scott Moser <email address hidden> wrote:

> could you please attach /var/log/cloud-init.log and output of
> 'ec2metadata --userdata' on the instance that has had the problem.
>
> also, is this 100% reproducible?
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1163669
>
> Title:
> cloud-init fails to install juju agent after bootstrap
>
> Status in “cloud-init” package in Ubuntu:
> Confirmed
>
> Bug description:
> output of cloud-init
> http://paste.ubuntu.com/5672490/
>
> ProblemType: Bug
> DistroRelease: Ubuntu 13.04
> Package: cloud-init 0.7.2~bzr804-0ubuntu1
> ProcVersionSignature: User Name 3.8.0-12.21-generic 3.8.2
> Uname: Linux 3.8.0-12-generic x86_64
> ApportVersion: 2.9.2-0ubuntu5
> Architecture: amd64
> Date: Wed Apr 3 03:26:10 2013
> Ec2AMI: ami-1e831d77
> Ec2AMIManifest: (unknown)
> Ec2AvailabilityZone: us-east-1c
> Ec2InstanceType: m1.small
> Ec2Kernel: aki-88aa75e1
> Ec2Ramdisk: unavailable
> MarkForUpload: True
> PackageArchitecture: all
> ProcEnviron:
> TERM=xterm
> PATH=(custom, no user)
> LANG=en_US.UTF-8
> SHELL=/bin/bash
> SourcePackage: cloud-init
> UpgradeStatus: No upgrade log present (probably fresh install)
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/cloud-init/+bug/1163669/+subscriptions
>

[Scott Moser (smoser)]

a couple of things seem odd. I originally suspected bug 1103881.
However, the log shows:
The following packages have been kept back:
  initramfs-tools initramfs-tools-bin libdevmapper1.02.1 libgudev-1.0-0
  linux-headers-generic linux-headers-virtual linux-image-virtual
  linux-virtual mountall python python-minimal upstart

Which is odd.

It seems like this is possibly related though, as I think the same issue. I dont think that the runcmd were ever executed.

ZhengPeng, could you try the same thing with a daily ami? ami-daa4c1b3 is currently the latest ami for amd64 ebs raring.

[Scott Moser (smoser)]

Looking a bit further, I'm pretty sure this is a different form of bug 1103881. This form is because libc was upgraded, and, as it is a dependency of upstart, it invokes 'telinit u', which restarts upstart and loses state.