Routed provider networks: placement API handling errors
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Lajos Katona |
Bug Description
Routed provider networks is a feature which uses placement to store information about segments, the subnets in segments and make possible that nova can use this information in scheduling.
On master the placement API calls are failing, at first at get_inventory call:
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
...
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
May 09 14:15:26 multicont neutron-
Using stable/pike (not just for neutron) the syncing is OK.
I suppose as the placement client code was moved to neutron-lib and changed to work with placement 1.20 something happened that makes routed networks placement calls failing.
Some details:
Used reproduction steps: https:/
neutron: d0e64c61835801a
neutron-lib: bcd898220ff53b3
placement: 570262556156791
nova: 56fef7c0e74d751
Ubuntu 18.04.2 LTS based multihost devstack
Queens is OK, on Monday I will check with Rocky.