Description of problem:
Customer complained about timeouts when opening admin/networks tab and we tried to understand what is going one and why requests time out. We focused on dashboard/admin/networks/ (customer also complained about instance's list).
Here are our findings:
- single v2.0/extensions -X GET
- single v2.0/networks -X GET (took around 7 seconds)
- single v2.0/subnets -X GET (around 2 seconds)
- 894 requests for NEUTRON v2.0/networks/UUID/dhcp-agents (took 36 seconds total)
- 336 requests for v2.0/quotas/ID/details (took 63 seconds total)
Here are the problems with this approach:
- Horizon uses information about number of DHCP agents to fill one of columns, but after switching to OVN most networks have 0 agents. So it is unclear why we really need this column at such cost.
- Horizon uses information about quotas to decide if admin can create a subnet or not using "Create Subnet" button. Again, it looks like cost is too high.
- Horizon makes requests one by one instead of making them in batches. In customer's environment there are 3 neutron servers with 12 workers each, most customers also run environments with multiple workers, so making more than 1200 requests one by one doesn't look like an optimal strategy.
Version-Release number of selected component (if applicable):
Red Hat OpenStack Platform release 16.2.4 (Train)
How reproducible:
Create numerous networks and projects, open admin/networks tab.
Actual results:
More than 90 seconds are spent to obtain minor details about amount of DHCP agents and subnet quotas, this causes timeout in deployments with default Timeout settings.
Expected results:
No timeout because information about networks and subnets is obtained in 10 seconds
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory (Red Hat OpenStack Platform 16.2 bug fix advisory), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2025:0200