Created subnets on ONE network that duplicated CIDR in case of neutron server active-active
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Nam |
Bug Description
I had three controllers. I found a bug. I can create subnets on one network that duplicated CIDR range AT SAME TIMING
How to reproduce:
Topology : http://
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands AT SAME TIMMING
- On controller1:
$ neutron subnet-create --name test-subnet1 test-net 192.168.100.0/24
- On controller2:
$ neutron subnet-create --name test-subnet2 test-net 192.168.100.0/24
After check subnet-list:
Running command: $ neutron subnet-list
This is the result: http://
Running command: $ neutron net-list
This is the result: http://
After check database:
This is the result: http://
I think. In originally, one command on controller will be fail and we catch a message as following: "Invalid input for operation: Requested subnet with cidr: 192.168.100.0/24 for network: 39cc0850-
Changed in neutron: | |
assignee: | nobody → Nam (namnh) |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
summary: |
- Created subnets on one network that duplicated CIDR in case of neutron + Created subnets on ONE network that duplicated CIDR in case of neutron server active-active |
description: | updated |
description: | updated |
description: | updated |
Changed in neutron: | |
assignee: | Nam (namnh) → nobody |
Changed in neutron: | |
assignee: | nobody → lane (lane-l) |
Changed in neutron: | |
assignee: | lane (lane-l) → Nam (namnh) |
assignee: | Nam (namnh) → nobody |
Changed in neutron: | |
assignee: | nobody → Nam (namnh) |
tags: | added: needs-attention |
Changed in neutron: | |
status: | Confirmed → In Progress |
Changed in neutron: | |
assignee: | Nam (namnh) → Mike Bayer (zzzeek) |
Changed in neutron: | |
assignee: | Mike Bayer (zzzeek) → Nam (namnh) |
Confirmed on devstack all-in-one setup with one neutron-server and api_workers > 0, which is the default devstack setup.
http:// paste.openstack .org/show/ 483424/
It failed once (As expected) with a duplicate CIDR error, but the second time I ran it I didn't get an error and had the same CIDR twice on the same network.