Comment 12 for bug 1674946

Using the package from yakkety-proposed in a yakkety LXD container:

$ lxc exec y1-proposed -- /bin/bash
root@y1-proposed:~# apt-cache policy cloud-init
cloud-init:
  Installed: 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1
  Candidate: 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1
  Version table:
 *** 0.7.9-90-g61eb03fe-0ubuntu1~16.10.1 500
        500 http://archive.ubuntu.com/ubuntu yakkety-proposed/main amd64 Packages

/config-drive with a link of type "dvs":
$ lxc exec y1-proposed -- grep dvs /config-drive/openstack/latest/network_data.json
   "type": "dvs",

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

logs clean too:
$ lxc exec y1-proposed -- grep dvs /var/log/cloud-init.log
$

To make sure my config-drive was being used, I injected a failure by setting an unknown link type of "dvs-andreas-was-here-again":
$ lxc file pull y1-proposed/run/cloud-init/result.json -
{
 "v1": {
  "datasource": null,
  "errors": [
   "Unknown network_data link type: dvs-andreas-was-here-again",
   "Unknown network_data link type: dvs-andreas-was-here-again",
   "('ssh-authkey-fingerprints', KeyError('getpwnam(): name not found: ubuntu',))"
  ]
 }
}

(the ssh authkey error is irrelevant for this case: the ubuntu user isn't created because of the network_data link type error)

and

$ lxc exec y1-proposed -- grep dvs-andreas-was-here-again /var/log/cloud-init.log
ValueError: Unknown network_data link type: dvs-andreas-was-here-again
ValueError: Unknown network_data link type: dvs-andreas-was-here-again