414 Request-Too-Long when using _get_sharing_providers with a large number of UUIDs

[Sahid Orentino]

The scheduler is reporting error when calling placement in situation of hosts running into many aggregates

The web server returns a 414 Request-Too-Long error because the size of the URL in the GET request exceeds the allowed limit.

The proposed fix is some modifications in _get_sharing_providers function to divide the agg_uuids list into groups of a maximum of 100 UUIDs per GET request. The division ensures that the size of each request remains below the allowed limit, resolving the issue of the 414 Request-Too-Long error.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/nova/+/921665

[sean mooney (sean-k-mooney)]

this is a feature not a bug setting the triage state to opinion

[sean mooney (sean-k-mooney)]

talksing about this a little more on irc

this issue is in the resource tracker not the scheduled as i orgianlly thought
this is similar to https://bugzilla.redhat.com/show_bug.cgi?id=2283075

currently the resource tracker is caching the set of sharing agggates it is a part of.

in some cases this is very large and can hit limits in the loadblancer or webserver.

sahid's proposal is to paginate the request which may be valided.

currently its not clear that the cached data in the resouce tracker is actually required and as such removal of this cached data might also be an option.

setting this to medium as the work around for now is to increase the max request size on the webserver or loadbalnacer.

the current limit is deployment tool specififc.