yahoo-eng-team team mailing list archive

[Shiv Prasad Rao <shivrao@xxxxxxxxx>]

Public bug reported:

When concurrent requests come from multiple tenants for network
creation, neutron allows to create two network segment with same BD
(vlan id and vxlan id)

Expected behaviour :  Should not reuse same bd


[root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 164ff80d-4104-4f8c-a610-9ae32bfcab85
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| id                        | 164ff80d-4104-4f8c-a610-9ae32bfcab85 |
| n1kv:member_segments      |                                      |
| n1kv:profile_id           | 1b5212d6-ac5b-4a07-9efe-0f97d0a8cae6 |
| name                      | net-t3-p1-s1                         |
| provider:network_type     | vlan                                 |
| provider:physical_network | p1                                   |
| provider:segmentation_id  | 1412                                 |
| router:external           | False                                |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   | 4ceded0e-54df-43fd-a229-adc8089ed6e1 |
| tenant_id                 | 41c08065e4c247c5b43baff041b20c71     |
+---------------------------+--------------------------------------+
[root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 128d1345-f152-4c18-9005-0fd119c263db
+---------------------------+--------------------------------------+
| Field                     | Value                                |
+---------------------------+--------------------------------------+
| admin_state_up            | True                                 |
| id                        | 128d1345-f152-4c18-9005-0fd119c263db |
| n1kv:member_segments      |                                      |
| n1kv:profile_id           | 1b5212d6-ac5b-4a07-9efe-0f97d0a8cae6 |
| name                      | net-t2-p1-s1                         |
| provider:network_type     | vlan                                 |
| provider:physical_network | p1                                   |
| provider:segmentation_id  | 1412                                 |
| router:external           | False                                |
| shared                    | False                                |
| status                    | ACTIVE                               |
| subnets                   | 72ee84b5-fb4e-43c0-85a4-dccc002b7ff9 |
| tenant_id                 | d31bcc1cc614426e888f02506c7d6197     |
+---------------------------+--------------------------------------+

** Affects: neutron
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1396387

Title:
  cisco n1kv: segment allocation table retrieves same segment id on
  concurrent requests

Status in OpenStack Neutron (virtual network service):
  New

Bug description:
  When concurrent requests come from multiple tenants for network
  creation, neutron allows to create two network segment with same BD
  (vlan id and vxlan id)

  Expected behaviour :  Should not reuse same bd

  
  [root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 164ff80d-4104-4f8c-a610-9ae32bfcab85
  +---------------------------+--------------------------------------+
  | Field                     | Value                                |
  +---------------------------+--------------------------------------+
  | admin_state_up            | True                                 |
  | id                        | 164ff80d-4104-4f8c-a610-9ae32bfcab85 |
  | n1kv:member_segments      |                                      |
  | n1kv:profile_id           | 1b5212d6-ac5b-4a07-9efe-0f97d0a8cae6 |
  | name                      | net-t3-p1-s1                         |
  | provider:network_type     | vlan                                 |
  | provider:physical_network | p1                                   |
  | provider:segmentation_id  | 1412                                 |
  | router:external           | False                                |
  | shared                    | False                                |
  | status                    | ACTIVE                               |
  | subnets                   | 4ceded0e-54df-43fd-a229-adc8089ed6e1 |
  | tenant_id                 | 41c08065e4c247c5b43baff041b20c71     |
  +---------------------------+--------------------------------------+
  [root@macc81f66b8f486 latest_os_sanity(openstack_admin)]# neutron net-show 128d1345-f152-4c18-9005-0fd119c263db
  +---------------------------+--------------------------------------+
  | Field                     | Value                                |
  +---------------------------+--------------------------------------+
  | admin_state_up            | True                                 |
  | id                        | 128d1345-f152-4c18-9005-0fd119c263db |
  | n1kv:member_segments      |                                      |
  | n1kv:profile_id           | 1b5212d6-ac5b-4a07-9efe-0f97d0a8cae6 |
  | name                      | net-t2-p1-s1                         |
  | provider:network_type     | vlan                                 |
  | provider:physical_network | p1                                   |
  | provider:segmentation_id  | 1412                                 |
  | router:external           | False                                |
  | shared                    | False                                |
  | status                    | ACTIVE                               |
  | subnets                   | 72ee84b5-fb4e-43c0-85a4-dccc002b7ff9 |
  | tenant_id                 | d31bcc1cc614426e888f02506c7d6197     |
  +---------------------------+--------------------------------------+

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1396387/+subscriptions