neutron

  1. Bug #1929190
  2. Comment #0

Comment 0 for bug 1929190

Revision history for this message
Rodolfo Alonso (rodolfo-alonso-hernandez) wrote :

Since [1], the VLAN segment allocation using "get_random_unallocated_segment" does not enforce a priority in the physical network selection, depending on the configuration order. All available physical network segments can be selected randomly; that means any physical network can be chosen.

The occurrence of this error was low because "phys_net1" has 4096 VLAN IDs and "phys_net2" only 10.

[1]https://review.opendev.org/c/openstack/neutron/+/780802