"type: local" doesn't work in host with kernel option 'ds=nocloud'

Bug #1195537 reported by Jian Wen on 2013-06-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
pyjuju
Low
Unassigned

Bug Description

Because cloud-init in the juju booted lxc instance parses the kernel args by reading /proc/cmdline.
The lxc instance has the same /proc/cmdline with its host, so it reads '... ds=nocloud ...'.
In the lxc instance, juju and its friends will not be installed,
and /etc/init/juju-SERVICE-ID.conf will not be created.

Relate files in the instance:
/var/lib/cloud/instances/nocloud/datasource
/var/lib/cloud/instances/nocloud/obj.pkl

Related code:
cloudinit/DataSourceNoCloud.py

cloud-init's version is 0.6.3-0ubuntu1

How to reproduce:
1. Boot a precise cloud image as the juju host with kernel args
    "root=/dev/vda ro console=ttyS0 init=/usr/lib/cloud-init/uncloud-init ds=nocloud ubuntu-pass=ubuntu"
    Install linux-image-extra-virtual in the host

    You can use the following code to do so
    bzr branch lp:~wenjianhn/+junk/vbuntu

2. In the instance, deploy mysql
    http://paste.ubuntu.com/5806583/

The agent state will be infinite pending.

Workaround:
1. apt-get remove cloud-init in the juju host
2. boot the host without "init=/usr/lib/cloud-init/uncloud-init ds=nocloud ubuntu-pass=ubuntu"
3. juju time

Curtis Hovey (sinzui) on 2013-10-12
Changed in juju:
importance: Undecided → Low
status: New → Triaged
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers