yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #87238
[Bug 1944948] [NEW] IPv6 slaac subnet creation causes FixedIpsSubnetsNotOnSameSegment error
Public bug reported:
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
** Affects: neutron
Importance: Undecided
Assignee: Elvira García Ruiz (elviragr)
Status: New
** Description changed:
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
+ $ 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
+ $ 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.
+ 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)
+ - Devstack (Neutron master)
- OVN 21.03
There's a Bugzilla about this topic [0]
[0] https://bugzilla.redhat.com/show_bug.cgi?id=1939601
** Changed in: neutron
Assignee: (unassigned) => Elvira García Ruiz (elviragr)
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1944948
Title:
IPv6 slaac subnet creation causes FixedIpsSubnetsNotOnSameSegment
error
Status in neutron:
New
Bug 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
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1944948/+subscriptions
Follow ups