Comment 23 for bug 1673411

Revision history for this message
Andreas Hasenack (ahasenack) wrote :

Verified on yakkety with a yakkety lxd container and the provided instructions:

 *** 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1 500
        500 http://archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 Packages

Created a config-drive and verified the result.json file:

$ lxc file pull $name/run/cloud-init/result.json -
{
 "v1": {
  "datasource": "DataSourceConfigDrive [net,ver=2][source=/config-drive]",
  "errors": []
 }
}

/config-drive was there:
root@foohost:~# find /config-drive/ -type f
/config-drive/openstack/latest/meta_data.json
/config-drive/openstack/latest/network_data.json
/config-drive/openstack/latest/vendor_data.json
/config-drive/openstack/latest/user_data
/config-drive/openstack/2015-10-15/network_data.json
/config-drive/openstack/2015-10-15/user_data
/config-drive/openstack/2015-10-15/vendor_data.json
/config-drive/openstack/2015-10-15/meta_data.json

To be sure my config-drive was being read, in another attempt I injected a failure into it by setting a link of an unknown type:

$ lxc file pull $name/run/cloud-init/result.json -
{
 "v1": {
  "datasource": null,
  "errors": [
   "Unknown network_data link type: dvs-andreas-was-here",
   "Unknown network_data link type: dvs-andreas-was-here",
   "('ssh-authkey-fingerprints', KeyError('getpwnam(): name not found: ubuntu',))"
  ]
 }
}

As a side note, that prevented the ubuntu user from being created (and probably other things which do not concern us here).