← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1642679] Re: The OpenStack network_config.json implementation fails on Hyper-V compute nodes

 

Reviewed:  https://review.openstack.org/400883
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f559be35a03f5801f527355895a97c89cdc3c336
Submitter: Jenkins
Branch:    master

commit f559be35a03f5801f527355895a97c89cdc3c336
Author: Scott Moser <smoser@xxxxxxxxxxxx>
Date:   Fri Mar 31 17:01:33 2017 -0400

    Limit exposure of network device types to the guest.
    
    Previously, the 'type' of the hypervisor network device, was exposed to
    the guest directly. That does not make sense, as
    a.) this leaks needless information into the guest
    b.) the guest cannot be reasonably expected to make decisions
        based on a type of link that is present underneath the
        virtual device that is presented to the guest.
    c.) guests then are forced to either continuously track these types
        or to assume that unknown type is "phy".
    
    This limits the exposure of types to a specific list. Any other
    type will be shown to the guest as 'phy'.
    
    Change-Id: Iea458fba29596cd2773d8d3565451af60b02bcca
    Closes-Bug: #1642679


** Changed in: nova
       Status: In Progress => Fix Released

-- 
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/1642679

Title:
  The OpenStack network_config.json implementation fails on Hyper-V
  compute nodes

Status in cloud-init:
  Fix Released
Status in OpenStack Compute (nova):
  Fix Released
Status in cloud-init package in Ubuntu:
  Fix Released
Status in cloud-init source package in Xenial:
  Fix Released
Status in cloud-init source package in Yakkety:
  Fix Released

Bug description:
  === Begin SRU Template ===
  [Impact]
  When a config drive provides network_data.json on Azure OpenStack,
  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.
  === End SRU Template ===

  We have discovered an issue when booting Xenial instances on OpenStack
  environments (Liberty or newer) and Hyper-V compute nodes using config
  drive as metadata source.

  When applying the network_config.json, cloud-init fails with this error:
  http://paste.openstack.org/show/RvHZJqn48JBb0TO9QznL/

  The fix would be to add 'hyperv' as a link type here:
  /usr/lib/python3/dist-packages/cloudinit/sources/helpers/openstack.py, line 587

  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/1642679/+subscriptions


References