Fullstack tests failing due to "hang" neutron-server process
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
High
|
Rodolfo Alonso |
Bug Description
From time to time some fullstack tests are failing and it seems that the problem is with not responding neutron-server process.
There is almost nothing in neutron-server's logs in such case.
Example of such failure: https:/
neutron-server logs (https:/
2020-02-05 11:00:36.851 3180 INFO neutron.
2020-02-05 11:00:36.852 3180 INFO neutron.
2020-02-05 11:00:37.796 3180 INFO neutron.
2020-02-05 11:00:37.797 3180 INFO neutron.
2020-02-05 11:01:11.476 3180 INFO neutron.
2020-02-05 11:01:11.479 3180 INFO neutron.
2020-02-05 11:01:11.480 3180 INFO neutron.
So it seems that it didn't initialize properly ml2 extension drivers and mechanism drivers.
tags: | added: neutron-proactive-backport-potential |
tags: | removed: neutron-proactive-backport-potential |
Changed in neutron: | |
status: | Fix Committed → Fix Released |
Hello:
Reviewing the logs and executing the Neutron server initialization with a profiler, the VLAN driver most time consuming operation is the retrieval of all VLAN allocations from the DB [1]. This can take several seconds in a loaded system.
Usually the number of VLANs per physnet is >1000. In fullstack tests we can reduce this number [2] in order to reduce the number of registers in the DB.
We can also improve the way the VLAN driver is handling those registers:
- Retrieve only those ones with physical_network == ranges networks.
- Delete the VLAN registers with unused physical network in a bulk operation.
Regards.
[1] https:/ /github. com/openstack/ neutron/ blob/de0d9da2fe 9431401b2829230 18f80c195bdaf55 /neutron/ plugins/ ml2/drivers/ type_vlan. py#L109 /github. com/openstack/ neutron/ blob/de0d9da2fe 9431401b2829230 18f80c195bdaf55 /neutron/ tests/fullstack /resources/ config. py#L176
[2] https:/