Debian-format IPv6 information is not offered by the OpenStack HTTP metadata service.

[Paula Crismaru]

Debian-format IPv6 information is not offered by the OpenStack HTTP metadata service.

The debian-format IPv6 network information is not offered by the HTTP Openstack metadata, whereas the metadata is present in the config drive.

Content of http://169.254.169.254/openstack/content/0000:

# Injected by Nova on instance boot
#
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
    hwaddress ether fa:16:3e:8f:df:6f
    address 10.100.0.4
    netmask 255.255.255.240
    broadcast 10.100.0.15
    gateway 10.100.0.1
    dns-nameservers 8.8.8.8 8.8.4.4

Content of <config_drive_mount_point>/openstack/content/0000 for the same instance:
# Injected by Nova on instance boot
#
# This file describes the network interfaces available on your system
# and how to activate them. For more information, see interfaces(5).

# The loopback network interface
auto lo
iface lo inet loopback

auto eth1
iface eth1 inet static
    hwaddress ether fa:16:3e:8f:df:6f
    address 10.100.0.4
    netmask 255.255.255.240
    broadcast 10.100.0.15
    gateway 10.100.0.1
    dns-nameservers 8.8.8.8 8.8.4.4
iface eth1 inet6 static
    hwaddress ether fa:16:3e:8f:df:6f
    address ::ffff:10.0.0.2
    netmask 120
    gateway ::ffff:10.0.0.1
    dns-nameservers ::ffff:808:808 ::ffff:808:404

Steps to reproduce:
- create neutron network net1
- create an IPv4 subnet for net1, with DHCP disabled
- create an IPv6 subnet for net1, with DHCP disabled
- create another network - net0, and add to it an ipv4 subnet with dhcp enabled, so that http metadata can be accessed
- boot a vm with net0 as the first network and net1 as the second network

Actual result:
- Debian-format IPv6 information is not present in the HTTP metadata

Expected result:
- IPv6 information should be present in the HTTP metadata, as it is in the config drive

Environment:
- OpenStack Mitaka installed via Juju charms
- Nova version: 13.1.2
- Neutron version: 8.3.0
- Hypervisor: KVM
- VM: Windows Server 2012R2 or higher

[Sean Dague (sdague)]

Can you confirm that this is the behavior on master as well? Mitaka is now eol.

[Launchpad Janitor (janitor)]

[Expired for OpenStack Compute (nova) because there has been no activity for 60 days.]