[Bug 1469260] Re: Custom vendor data causes cloud-init failure on 0.7.5

Felipe Reyes 1469260 at bugs.launchpad.net
Thu Jul 23 19:22:52 UTC 2015


A vendor data file should be a dict with a cloud-init key and the value
for that key is expected to be a string or a list[0], the docs provide a
simple example[1]

Here is another example that will add a user called cloudy, upgrade the
system and install htop:

{"cloud-init": "#cloud-config\nusers:\n - name: cloudy\n   ssh-import-
id: cloudy\npackage_upgrade: True\npackages:\n - htop"}

So a yaml cloud-config compatible has to be passed a string.

[0] http://bazaar.launchpad.net/~cloud-init-dev/cloud-init/trunk/view/head:/cloudinit/sources/helpers/openstack.py#L470
[1] http://cloudinit.readthedocs.org/en/latest/topics/datasources.html?highlight=vendor#vendor-data

-- 
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to cloud-init in Ubuntu.
https://bugs.launchpad.net/bugs/1469260

Title:
  Custom vendor data causes cloud-init failure on 0.7.5

To manage notifications about this bug go to:
https://bugs.launchpad.net/cloud-init/+bug/1469260/+subscriptions



More information about the Ubuntu-server-bugs mailing list