I've dropped the nova task.
This will be fixed in nova hopefully under bug 1642679.
My merge proposal is at https://review.openstack.org/#/c/400883

** No longer affects: nova

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1674946

Title:
  cloud-init fails with "Unknown network_data link type: dvs"

Status in cloud-init:
  Fix Committed
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Confirmed
Status in cloud-init source package in Yakkety:
  Confirmed

Bug description:
  === Begin SRU Template ===
  [Impact]
  When a config drive provides network_data.json on Openstack running on
  ESXi cloud-init will fail to configure networking.

  Console log and /var/log/cloud-init.log will show:
   ValueError: Unknown network_data link type: hyperv

  This woudl also occur when the type of the network device as declared
  to cloud-init was 'hw_veb', 'hyperv', or 'vhostuser'.

  [Test Case]
  Launch an instance with config drive on hyperv cloud.

  [Regression Potential]
  Low to none. cloud-init is relaxing requirements and will accept things
  now that it previously complained were invalid.

  This is very similar to change in bug 1642679.
  Upstream Openstack Merge proposal to stop this from continually
  happening at https://review.openstack.org/#/c/400883/
  === End SRU Template ===

  When booting an OpenStack instance, cloud-init fails with:

  [   33.307325] cloud-init[445]: Cloud-init v. 0.7.9 running 'init-local' at 
Mon, 20 Mar 2017 14:42:58 +0000. Up 31.06 seconds.
  [   33.368434] cloud-init[445]: 2017-03-20 14:43:00,779 - util.py[WARNING]: 
failed stage init-local
  [   33.449886] cloud-init[445]: failed run of stage init-local
  [   33.490863] cloud-init[445]: 
------------------------------------------------------------
  [   33.542214] cloud-init[445]: Traceback (most recent call last):
  [   33.585204] cloud-init[445]:   File 
"/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 513, in 
status_wrapper
  [   33.654579] cloud-init[445]:     ret = functor(name, args)
  [   33.696372] cloud-init[445]:   File 
"/usr/lib/python3/dist-packages/cloudinit/cmd/main.py", line 269, in main_init
  [   33.755593] cloud-init[445]:     
init.apply_network_config(bring_up=bool(mode != sources.DSMODE_LOCAL))
  [   33.809124] cloud-init[445]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 622, in 
apply_network_config
  [   33.847161] cloud-init[445]:     netcfg, src = 
self._find_networking_config()
  [   33.876562] cloud-init[445]:   File 
"/usr/lib/python3/dist-packages/cloudinit/stages.py", line 609, in 
_find_networking_config
  [   33.916335] cloud-init[445]:     if self.datasource and 
hasattr(self.datasource, 'network_config'):
  [   33.956207] cloud-init[445]:   File 
"/usr/lib/python3/dist-packages/cloudinit/sources/DataSourceConfigDrive.py", 
line 147, in network_config
  [   34.008213] cloud-init[445]:     self.network_json, 
known_macs=self.known_macs)
  [   34.049714] cloud-init[445]:   File 
"/usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py", line 
627, in convert_net_json
  [   34.104226] cloud-init[445]:     'Unknown network_data link type: %s' % 
link['type'])
  [   34.144219] cloud-init[445]: ValueError: Unknown network_data link type: 
dvs
  [   34.175934] cloud-init[445]: 
------------------------------------------------------------

  I am using Neutron with the Simple DVS plugin.

  Related bugs:
   * bug 1674946: cloud-init fails with "Unknown network_data link type: dvs
   * bug 1642679: OpenStack network_config.json implementation fails on Hyper-V 
compute nodes

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

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to     : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp

Reply via email to