Public bug reported: Description ===========
The use_ipv6 flag is marked as deprecated in the Ocata release (https://docs.openstack.org/ocata/config-reference/compute/config-options.html ) because it Nova networking is planed to be removed. However this flag also influences the data generated in the network_data.json. If the flag is set to false the IPv6 networks are missing from the JSON. If the value is true the JSON contains the IPv6 interfaces. Further details can be found here: https://bugs.launchpad.net/nova/+bug/1514082 If default value (false) is also inconsistent with the data returned by Neutron through the meta data service. http://169.254.169.254/openstack/latest/network_data.json Steps to reproduce ================== 1. Boot a server with 2 interfaces one IPv4 and one IPv6 2. mount /dev/sr0 /mnt 3. The /mnt/openstack/latest/network-data.json does not contain IPv6 addresses 0. Change the use_ipv6 flag to true on all compute nodes and restart the compute service 1. Boot a server with 2 interfaces one IPv4 and one IPv6 2. mount /dev/sr0 /mnt 3. The /mnt/openstack/latest/network-data.json does not contain IPv6 addresses Expected result =============== Option 1: Change the description of the use_ipv6 to: "Configures if the IPv6 addresses should be included in the config drive. (Remove deprecation warning) Change the default value to true to be in sync with neutron behaviour. Option 2: The generation of the network-data.json on config drive should always include the IPv6 addresses. ** Affects: nova Importance: Undecided Status: New -- 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/1704458 Title: The use_ipv6 flag not only influences nova networking Status in OpenStack Compute (nova): New Bug description: Description =========== The use_ipv6 flag is marked as deprecated in the Ocata release (https://docs.openstack.org/ocata/config-reference/compute/config-options.html ) because it Nova networking is planed to be removed. However this flag also influences the data generated in the network_data.json. If the flag is set to false the IPv6 networks are missing from the JSON. If the value is true the JSON contains the IPv6 interfaces. Further details can be found here: https://bugs.launchpad.net/nova/+bug/1514082 If default value (false) is also inconsistent with the data returned by Neutron through the meta data service. http://169.254.169.254/openstack/latest/network_data.json Steps to reproduce ================== 1. Boot a server with 2 interfaces one IPv4 and one IPv6 2. mount /dev/sr0 /mnt 3. The /mnt/openstack/latest/network-data.json does not contain IPv6 addresses 0. Change the use_ipv6 flag to true on all compute nodes and restart the compute service 1. Boot a server with 2 interfaces one IPv4 and one IPv6 2. mount /dev/sr0 /mnt 3. The /mnt/openstack/latest/network-data.json does not contain IPv6 addresses Expected result =============== Option 1: Change the description of the use_ipv6 to: "Configures if the IPv6 addresses should be included in the config drive. (Remove deprecation warning) Change the default value to true to be in sync with neutron behaviour. Option 2: The generation of the network-data.json on config drive should always include the IPv6 addresses. To manage notifications about this bug go to: https://bugs.launchpad.net/nova/+bug/1704458/+subscriptions -- Mailing list: https://launchpad.net/~yahoo-eng-team Post to : [email protected] Unsubscribe : https://launchpad.net/~yahoo-eng-team More help : https://help.launchpad.net/ListHelp
