2021-09-24 09:32:12 |
Elvira García Ruiz |
bug |
|
|
added bug |
2021-09-24 09:33:17 |
Elvira García Ruiz |
description |
When tries to create IPv6 SLAAC subnet in multisegment network it raises the FixedIpsSubnetsNotOnSameSegment error. But the subnet is actually created.
Steps to reproduce:
openstack network create --share --provider-network-type geneve --provider-segment 777 test_net
SEGMENT=`openstack network segment list --network test_net | awk '/777/ {print $2}'`
openstack network segment set --name segment777 $SEGMENT
openstack network segment create --network-type geneve --segment 778 --network test_net segment778
openstack subnet create --network test_net --network-segment segment777 --ip-version 4 --subnet-range 10.77.7.0/24 --dhcp segment777-v4
openstack subnet create --network test_net --network-segment segment778 --ip-version 4 --subnet-range 10.77.8.0/24 --dhcp segment778-v4
openstack subnet create --network test_net --network-segment segment777 --ip-version 6 --subnet-range 2001:10:77:7::/64 --dhcp --ipv6-address-mode slaac segment777-v6
Expected result:
Subnet created with no errors
Actual result:
Subnet created, but API throws an exception:
BadRequestException: 400: Client Error for url: http://10.0.0.105:9696/v2.0/subnets, Cannot allocate addresses from different segments.
Version:
- Devstack (Neutron master)
- OVN 21.03
There's a Bugzilla about this topic [0]
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1939601 |
When tries to create IPv6 SLAAC subnet in multisegment network it raises the FixedIpsSubnetsNotOnSameSegment error. But the subnet is actually created.
Steps to reproduce:
$ openstack network create --share --provider-network-type geneve --provider-segment 777 test_net
SEGMENT=`openstack network segment list --network test_net | awk '/777/ {print $2}'`
$ openstack network segment set --name segment777 $SEGMENT
$ openstack network segment create --network-type geneve --segment 778 --network test_net segment778
$ openstack subnet create --network test_net --network-segment segment777 --ip-version 4 --subnet-range 10.77.7.0/24 --dhcp segment777-v4
$ openstack subnet create --network test_net --network-segment segment778 --ip-version 4 --subnet-range 10.77.8.0/24 --dhcp segment778-v4
$ openstack subnet create --network test_net --network-segment segment777 --ip-version 6 --subnet-range 2001:10:77:7::/64 --dhcp --ipv6-address-mode slaac segment777-v6
Expected result:
Subnet created with no errors
Actual result:
Subnet created, but API throws an exception:
BadRequestException: 400: Client Error for url: http://10.0.0.105:9696/v2.0/subnets, Cannot allocate addresses from different segments.
Version:
- Devstack (Neutron master)
- OVN 21.03
There's a Bugzilla about this topic [0]
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1939601 |
|
2021-09-24 09:34:37 |
Elvira García Ruiz |
neutron: assignee |
|
Elvira García Ruiz (elviragr) |
|
2021-09-24 10:49:34 |
Bernard Cafarelli |
neutron: importance |
Undecided |
Medium |
|
2021-09-24 10:49:44 |
Bernard Cafarelli |
tags |
|
ipv6 ovn |
|
2021-09-24 12:05:55 |
Elvira García Ruiz |
neutron: status |
New |
In Progress |
|
2021-09-28 14:37:27 |
Elvira García Ruiz |
description |
When tries to create IPv6 SLAAC subnet in multisegment network it raises the FixedIpsSubnetsNotOnSameSegment error. But the subnet is actually created.
Steps to reproduce:
$ openstack network create --share --provider-network-type geneve --provider-segment 777 test_net
SEGMENT=`openstack network segment list --network test_net | awk '/777/ {print $2}'`
$ openstack network segment set --name segment777 $SEGMENT
$ openstack network segment create --network-type geneve --segment 778 --network test_net segment778
$ openstack subnet create --network test_net --network-segment segment777 --ip-version 4 --subnet-range 10.77.7.0/24 --dhcp segment777-v4
$ openstack subnet create --network test_net --network-segment segment778 --ip-version 4 --subnet-range 10.77.8.0/24 --dhcp segment778-v4
$ openstack subnet create --network test_net --network-segment segment777 --ip-version 6 --subnet-range 2001:10:77:7::/64 --dhcp --ipv6-address-mode slaac segment777-v6
Expected result:
Subnet created with no errors
Actual result:
Subnet created, but API throws an exception:
BadRequestException: 400: Client Error for url: http://10.0.0.105:9696/v2.0/subnets, Cannot allocate addresses from different segments.
Version:
- Devstack (Neutron master)
- OVN 21.03
There's a Bugzilla about this topic [0]
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1939601 |
When trying to create IPv6 SLAAC subnet in multisegment network Neutron raises the FixedIpsSubnetsNotOnSameSegment error. But the subnet is actually created.
Steps to reproduce:
$ openstack network create --share --provider-network-type geneve --provider-segment 777 test_net
SEGMENT=`openstack network segment list --network test_net | awk '/777/ {print $2}'`
$ openstack network segment set --name segment777 $SEGMENT
$ openstack network segment create --network-type geneve --segment 778 --network test_net segment778
$ openstack subnet create --network test_net --network-segment segment777 --ip-version 4 --subnet-range 10.77.7.0/24 --dhcp segment777-v4
$ openstack subnet create --network test_net --network-segment segment778 --ip-version 4 --subnet-range 10.77.8.0/24 --dhcp segment778-v4
$ openstack subnet create --network test_net --network-segment segment777 --ip-version 6 --subnet-range 2001:10:77:7::/64 --dhcp --ipv6-address-mode slaac segment777-v6
Expected result:
Subnet created with no errors
Actual result:
Subnet created, but API throws an exception:
BadRequestException: 400: Client Error for url: http://10.0.0.105:9696/v2.0/subnets, Cannot allocate addresses from different segments.
Version:
- Devstack (Neutron master)
- OVN 21.03
There's a Bugzilla about this topic [0]
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1939601 |
|
2021-10-04 16:43:14 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
2021-10-13 10:45:49 |
OpenStack Infra |
tags |
ipv6 ovn |
in-stable-wallaby ipv6 ovn |
|
2021-10-13 10:45:57 |
OpenStack Infra |
tags |
in-stable-wallaby ipv6 ovn |
in-stable-victoria in-stable-wallaby ipv6 ovn |
|
2021-10-13 10:48:43 |
OpenStack Infra |
tags |
in-stable-victoria in-stable-wallaby ipv6 ovn |
in-stable-ussuri in-stable-victoria in-stable-wallaby ipv6 ovn |
|
2021-10-15 15:13:48 |
OpenStack Infra |
tags |
in-stable-ussuri in-stable-victoria in-stable-wallaby ipv6 ovn |
in-stable-ussuri in-stable-victoria in-stable-wallaby in-stable-xena ipv6 ovn |
|
2021-10-15 15:13:54 |
OpenStack Infra |
tags |
in-stable-ussuri in-stable-victoria in-stable-wallaby in-stable-xena ipv6 ovn |
in-stable-train in-stable-ussuri in-stable-victoria in-stable-wallaby in-stable-xena ipv6 ovn |
|