← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1623813] Re: IPv6 network not shown in metadata

 

Gah, forgot there is a knob that needs turning in order to enable this.
Might be worth considering changing the default for this nowadays.

** Changed in: nova
       Status: New => Invalid

** Changed in: neutron
       Status: New => Invalid

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1623813

Title:
  IPv6 network not shown in metadata

Status in neutron:
  Invalid
Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Steps to reproduce:

  - Set up devstack with default settings from master
  - Start an instance using e.g. the default cirros-0.3.4 image
  - The instance will receive both an IPv4 and IPv6 address, but this isn't shown in the metadata, either on the configdrive or via http:

  stack@jr-t5:~/devstack$ nova list
  +--------------------------------------+-------+--------+------------+-------------+--------------------------------------------------------+
  | ID                                   | Name  | Status | Task State | Power State | Networks                                               |
  +--------------------------------------+-------+--------+------------+-------------+--------------------------------------------------------+
  | dfc9021e-b9d6-4b47-8bcf-d59d6b886a67 | test1 | ACTIVE | -          | Running     | private=10.1.0.6, fdc0:b675:211f:0:f816:3eff:fe03:5402 |
  +--------------------------------------+-------+--------+------------+-------------+--------------------------------------------------------+

  $ curl 169.254.169.254/openstack/latest/network_data.json;echo
  {"services": [], "networks": [{"network_id": "43e683d5-d3c8-4dd3-aab5-a279bbf6d049", "link": "tap5359dc4d-d0", "type": "ipv4_dhcp", "id": "network0"}], "links": [{"ethernet_mac_address": "fa:16:3e:03:54:02", "mtu": 1450, "type": "ovs", "id": "tap5359dc4d-d0", "vif_id": "53
  59dc4d-d04b-4a18-aab4-57b763c100af"}]} 
  $ cat /mnt/openstack/latest/network_data.json;echo
  {"services": [], "networks": [{"network_id": "43e683d5-d3c8-4dd3-aab5-a279bbf6d049", "link": "tap5359dc4d-d0", "type": "ipv4_dhcp", "id": "network0"}], "links": [{"ethernet_mac_address": "fa:16:3e:03:54:02", "mtu": 1450, "type": "ovs", "id": "tap5359dc4d-d0", "vif_id": "53
  59dc4d-d04b-4a18-aab4-57b763c100af"}]}    

  Expected result: The presence of an IPv6 network should be shown in
  the metadata, in order to allow the instance to enable or disable IPv6
  processing accordingly.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1623813/+subscriptions


References