Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1089447 - [RFE][neutron]: support multiple ipv6 prefixes for ipv6 network
[RFE][neutron]: support multiple ipv6 prefixes for ipv6 network
Status: CLOSED ERRATA
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-neutron (Show other bugs)
unspecified
Unspecified Unspecified
medium Severity medium
: z2
: 7.0 (Kilo)
Assigned To: Sridhar Gaddam
Eran Kuris
https://blueprints.launchpad.net/neut...
upstream_milestone_kilo-rc1 upstream_...
: FutureFeature, ZStream
Depends On: 1228176
Blocks: 1232677
  Show dependency treegraph
 
Reported: 2014-04-19 00:05 EDT by RHOS Integration
Modified: 2016-04-26 17:34 EDT (History)
10 users (show)

See Also:
Fixed In Version:
Doc Type: Enhancement
Doc Text:
This enhancement adds support for configuring multiple IPv6 prefixes and addresses on a single interface. As a result, OpenStack Networking (neutron) considers the type of IPv6 subnets that form part of the network, and automatically associates ports with addresses from all the SLAAC-enabled subnets within the ports network. There is no change to the REST API, but port-create/port-update responses automatically include the SLAAC addresses in the list of 'fixed_ips'.
Story Points: ---
Clone Of:
Environment:
Last Closed: 2015-10-08 08:07:15 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1866 normal SHIPPED_LIVE openstack-neutron bug fix advisory 2015-10-08 12:05:39 EDT

  None (edit)
Description RHOS Integration 2014-04-19 00:05:26 EDT
Cloned from launchpad blueprint https://blueprints.launchpad.net/neutron/+spec/multiple-ipv6-prefixes.

Description:

IPv6 allows multiple prefixes per network interface. This blueprint explores how to support them with neutron

Specification URL (additional information):

None
Comment 2 Eran Kuris 2015-06-03 05:32:54 EDT
Hi Sridhar ,  I finished to write the test plan and I attached it to "External Trackers". Please take a look for final review and tell me if you have any comments . thanks you very much .
Comment 3 Sridhar Gaddam 2015-06-04 00:23:49 EDT
Hello Eran,

I've emailed you the comments. Please take a look and update the document accordingly.

Thanks,
--Sridhar.
Comment 4 Eran Kuris 2015-06-04 07:17:13 EDT
This RFE cannot be tested because of blocker bug https://bugzilla.redhat.com/show_bug.cgi?id=1228176
in launchpad :
https://bugs.launchpad.net/neutron/+bug/1456206?comments=all

Tried to test it on :OSP 7 build 2015-06-02.1  on rhel 7.1
# rpm -qa |grep neutron 
python-neutron-2015.1.0-1.el7ost.noarch
openstack-neutron-openvswitch-2015.1.0-1.el7ost.noarch
python-neutronclient-2.4.0-1.el7ost.noarch
openstack-neutron-2015.1.0-1.el7ost.noarch
openstack-neutron-ml2-2015.1.0-1.el7ost.noarch
openstack-neutron-lbaas-2015.1.0-3.el7ost.noarch
python-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-fwaas-2015.1.0-3.el7ost.noarch
openstack-neutron-common-2015.1.0-1.el7ost.noarch
python-neutron-lbaas-2015.1.0-3.el7ost.noarch

test run : 
https://tcms.engineering.redhat.com/run/248773/
Comment 6 Sridhar Gaddam 2015-07-03 03:31:34 EDT
The blocker Bug reported for this issue is resolved by using dnsmasq 2.67 as well as the neutron patch which is merged upstream [1] and a stable/kilo patch under review [2].

[1] https://review.openstack.org/#/c/185066/
[2] https://review.openstack.org/#/c/197469/
Comment 7 Ihar Hrachyshka 2015-09-04 06:11:49 EDT
I believe it's included in >= openstack-neutron-2015.1.1-1.el7ost. If so, please mark as MODIFIED.
Comment 8 Sridhar Gaddam 2015-09-04 06:44:34 EDT
Yes @Ihar, stable/kilo patch is merged upstream and is available in >= openstack-neutron-2015.1.1-1.el7ost
Comment 11 Toni Freger 2015-09-17 02:49:13 EDT
Hi Ihar,

We can't close this bug because of the original one that still reproduces for us. Please see: https://bugzilla.redhat.com/show_bug.cgi?id=1228176

The latest build still works with dnsmasq-2.66-13.el7_1.src.rpm
Comment 12 Ihar Hrachyshka 2015-10-05 08:50:33 EDT
The bug Toni refers to is in VERIFIED.
Comment 13 Eran Kuris 2015-10-06 07:41:25 EDT
Verified on the latest kilo puddle 
[root@dell-c6220-11 ~(keystone_admin)]# rpm -qa |grep dnsmasq
dnsmasq-2.66-14.el7_1.x86_64
dnsmasq-utils-2.66-14.el7_1.x86_64
[root@dell-c6220-11 ~(keystone_admin)]# rpm -qa |grep neutron 
openstack-neutron-common-2015.1.1-6.el7ost.noarch
openstack-neutron-2015.1.1-6.el7ost.noarch
openstack-neutron-ml2-2015.1.1-6.el7ost.noarch
python-neutronclient-2.4.0-2.el7ost.noarch
openstack-neutron-lbaas-2015.1.1-1.el7ost.noarch
python-neutron-2015.1.1-6.el7ost.noarch
openstack-neutron-fwaas-2015.1.1-1.el7ost.noarch
python-neutron-lbaas-2015.1.1-1.el7ost.noarch
openstack-neutron-openvswitch-2015.1.1-6.el7ost.noarch
python-neutron-fwaas-2015.1.1-1.el7ost.noarch

VM nic for example: 
[root@host-192-168-1-4 ~]# ifconfig 
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1400
        inet 192.168.1.4  netmask 255.255.255.0  broadcast 192.168.1.255
        inet6 2003:db3::f816:3eff:fe01:971d  prefixlen 64  scopeid 0x0<global>
        inet6 2002:db2::f816:3eff:fe01:971d  prefixlen 64  scopeid 0x0<global>
        inet6 2001:db1::f816:3eff:fe01:971d  prefixlen 64  scopeid 0x0<global>
        inet6 fe80::f816:3eff:fe01:971d  prefixlen 64  scopeid 0x20<link>
        ether fa:16:3e:01:97:1d  txqueuelen 1000  (Ethernet)
        RX packets 531  bytes 50089 (48.9 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 319  bytes 30000 (29.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0


https://tcms.engineering.redhat.com/run/255169/
Comment 15 errata-xmlrpc 2015-10-08 08:07:15 EDT
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2015:1866

Note You need to log in before you can comment on or make changes to this bug.