| 2016-01-11 08:05:40 |
Nam |
bug |
|
|
added bug |
| 2016-01-11 08:07:30 |
Nam |
neutron: assignee |
|
Nam (namnh) |
|
| 2016-01-11 08:11:27 |
Nam |
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://codepad.org/WocbNR3d
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check database: http://codepad.org/MgVnOeJT |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check database: http://codepad.org/MgVnOeJT |
|
| 2016-01-11 08:12:50 |
Cao Xuan Hoang |
bug |
|
|
added subscriber Cao Xuan Hoang |
| 2016-01-11 08:28:47 |
Nam |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check database: http://codepad.org/MgVnOeJT |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check database: http://codepad.org/MgVnOeJT
Running command:
$ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ |
|
| 2016-01-11 08:36:28 |
Nam |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check database: http://codepad.org/MgVnOeJT
Running command:
$ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check subnet-list:
Running command: $ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ
Check database: http://codepad.org/MgVnOeJT |
|
| 2016-01-11 08:37:17 |
Nam |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check subnet-list:
Running command: $ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ
Check database: http://codepad.org/MgVnOeJT |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check subnet-list:
Running command: $ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ
After check database:
This is the result: http://codepad.org/MgVnOeJT |
|
| 2016-01-11 08:52:19 |
Nam |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check subnet-list:
Running command: $ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ
After check database:
This is the result: http://codepad.org/MgVnOeJT |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check subnet-list:
Running command: $ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ
After check database:
This is the result: http://codepad.org/MgVnOeJT
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.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
|
| 2016-01-11 10:10:44 |
Nam |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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/16
After check subnet-list:
Running command: $ neutron subnet-list
This is the result: http://codepad.org/ROYqkTdJ
After check database:
This is the result: http://codepad.org/MgVnOeJT
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.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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://codepad.org/3hyHy8Lk
After check database:
This is the result: http://codepad.org/WJVJYLDn
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.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
|
| 2016-01-11 10:20:04 |
Lubosz Kosnik |
marked as duplicate |
|
1271171 |
|
| 2016-01-11 10:35:29 |
Nam |
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://codepad.org/ff0debPB
Step 1: Create a network
$ neutron net-create test-net
Step 2: Create multiple subnets that duplicated CIDR scope
Please running commands at same timing
- 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://codepad.org/3hyHy8Lk
After check database:
This is the result: http://codepad.org/WJVJYLDn
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.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
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://codepad.org/ff0debPB
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://codepad.org/3hyHy8Lk
After check database:
This is the result: http://codepad.org/WJVJYLDn
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.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
|
| 2016-01-11 10:48:18 |
Nam |
summary |
Created subnets on one network that duplicated CIDR in case of neutron server active-active |
Created subnets on ONE network that duplicated CIDR in case of neutron server active-active |
|
| 2016-01-11 10:49:41 |
Lubosz Kosnik |
removed duplicate marker |
1271171 |
|
|
| 2016-01-11 11:24:57 |
Nam |
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://codepad.org/ff0debPB
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://codepad.org/3hyHy8Lk
After check database:
This is the result: http://codepad.org/WJVJYLDn
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.0.0/16 for network: 39cc0850-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
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://codepad.org/ff0debPB
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://codepad.org/3hyHy8Lk
After check database:
This is the result: http://codepad.org/WJVJYLDn
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-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
|
| 2016-01-11 11:45:25 |
Nam |
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://codepad.org/ff0debPB
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://codepad.org/3hyHy8Lk
After check database:
This is the result: http://codepad.org/WJVJYLDn
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-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
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://codepad.org/ff0debPB
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://codepad.org/306Vi90d
After check database:
This is the result: http://codepad.org/4qRC229P
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-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
|
| 2016-01-11 11:59:08 |
Nam |
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://codepad.org/ff0debPB
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://codepad.org/306Vi90d
After check database:
This is the result: http://codepad.org/4qRC229P
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-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
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://codepad.org/ff0debPB
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://codepad.org/306Vi90d
Running command: $ neutron net-list
This is the result: http://codepad.org/AcYRLP4b
After check database:
This is the result: http://codepad.org/4qRC229P
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-1eeb-4c85-bcdc-338a3f1461aa overlaps with another subnet.". But currently, two commands are success |
|
| 2016-01-11 13:35:53 |
Assaf Muller |
neutron: status |
New |
Confirmed |
|
| 2016-01-11 13:35:55 |
Assaf Muller |
neutron: importance |
Undecided |
High |
|
| 2016-01-11 13:38:43 |
Assaf Muller |
neutron: importance |
High |
Medium |
|
| 2016-01-11 13:39:00 |
Assaf Muller |
tags |
|
l3-ipam-dhcp |
|
| 2016-01-11 14:26:20 |
Nam |
neutron: assignee |
Nam (namnh) |
|
|
| 2016-01-11 15:02:16 |
lane |
neutron: assignee |
|
lane (lane-l) |
|
| 2016-01-11 16:20:38 |
Nam |
neutron: assignee |
lane (lane-l) |
Nam (namnh) |
|
| 2016-01-11 16:20:45 |
Nam |
neutron: assignee |
Nam (namnh) |
|
|
| 2016-01-12 02:36:34 |
Bo Chi |
bug |
|
|
added subscriber Bo Chi |
| 2016-01-13 02:45:07 |
Nam |
neutron: assignee |
|
Nam (namnh) |
|
| 2016-01-15 06:41:06 |
Nam |
bug |
|
|
added subscriber Nguyen Phuong An |
| 2016-01-18 18:18:14 |
Armando Migliaccio |
tags |
l3-ipam-dhcp |
l3-ipam-dhcp needs-attention |
|
| 2016-01-19 04:57:09 |
OpenStack Infra |
neutron: status |
Confirmed |
In Progress |
|
| 2016-01-20 21:45:33 |
Brian Haley |
bug |
|
|
added subscriber Brian Haley |
| 2016-01-20 22:02:10 |
Cedric Brandily |
bug |
|
|
added subscriber Cedric Brandily |
| 2016-06-27 18:34:54 |
OpenStack Infra |
neutron: assignee |
Nam (namnh) |
Mike Bayer (zzzeek) |
|
| 2016-07-07 09:47:59 |
OpenStack Infra |
neutron: assignee |
Mike Bayer (zzzeek) |
Nam (namnh) |
|
| 2016-09-01 07:38:30 |
OpenStack Infra |
neutron: status |
In Progress |
Fix Released |
|
