Public bug reported:
The fix was trying to use the created_at time to 'lock' the existing
segment range in DB. But it did not cover the situation that the
ml2_conf.ini changes the vlan_range. So, the vlan range will be
inconsistent between network segment range DB and ml2_conf.ini.
Another case is that in our produciton environment we found that there are
duplicated entry created in DB with completely same values:
+--------------------------------------+------+---------+--------+------------+--------------+------------------+---------+---------+------------------+
| id | name | default | shared | project_id |
network_type | physical_network | minimum | maximum | standard_attr_id |
+--------------------------------------+------+---------+--------+------------+--------------+------------------+---------+---------+------------------+
| 2c0097b7-d18c-4998-83e4-58e405a8ea11 | | 1 | 1 | NULL |
vlan | default | 200 | 3969 | 1311788 |
| a6046ac8-cfc2-4c7c-92a2-6f71d0acd9cc | | 1 | 1 | NULL |
vlan | default | 200 | 3969 | 1311791 |
+--------------------------------------+------+---------+--------+------------+--------------+------------------+---------+---------+------------------+
So, the better solution is to add DB uniq constrait with keys of
"network_type, physical_network, minimum, maximum", if duplicate entry
found, just ignore it.
** 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/2106463
Title:
network segment range initialization not updated
Status in neutron:
New
Bug description:
The fix was trying to use the created_at time to 'lock' the existing
segment range in DB. But it did not cover the situation that the
ml2_conf.ini changes the vlan_range. So, the vlan range will be
inconsistent between network segment range DB and ml2_conf.ini.
Another case is that in our produciton environment we found that there are
duplicated entry created in DB with completely same values:
+--------------------------------------+------+---------+--------+------------+--------------+------------------+---------+---------+------------------+
| id | name | default | shared | project_id
| network_type | physical_network | minimum | maximum | standard_attr_id |
+--------------------------------------+------+---------+--------+------------+--------------+------------------+---------+---------+------------------+
| 2c0097b7-d18c-4998-83e4-58e405a8ea11 | | 1 | 1 | NULL
| vlan | default | 200 | 3969 | 1311788 |
| a6046ac8-cfc2-4c7c-92a2-6f71d0acd9cc | | 1 | 1 | NULL
| vlan | default | 200 | 3969 | 1311791 |
+--------------------------------------+------+---------+--------+------------+--------------+------------------+---------+---------+------------------+
So, the better solution is to add DB uniq constrait with keys of
"network_type, physical_network, minimum, maximum", if duplicate entry
found, just ignore it.
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/2106463/+subscriptions
--
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help : https://help.launchpad.net/ListHelp
