+++ This bug was initially created as a clone of Bug #2267882 +++

Description of problem:

When customer visualize the content of a designate zone in the horizon dashboard, only 20 records are shown (without the possibility to view more entry).

Even if the designate zone have 70 recordset :
openstack recordset list --all-projects [dns domain] -f value -c name | wc -l
70

Version-Release number of selected component (if applicable):

How reproducible:

Open Horizon GUI and list the content of a zone

Actual results:

Only 20 record are displayed

Expected results:

same record amount of command below are displayed

~~~
openstack recordset list --all-projects [dns domain] -f value -c name | wc -l
~~~

Additional info:

Customer tried to change the number of element to visualize on the profile (from 20 to 50 for exemple) and doesn't work, they have changed the API_RESULT_PAGE_SIZE in horizon (from 20 to 50 doesn't work either)

— Additional comment from Michael Johnson on 2024-03-20 19:42:01 UTC —

The fix for this requires a new requirement for the designate-dashboard horizon plugin of openstacksdk.

Do we know if that is already present in the container that the designate-dashboard is installed into?
I suspect it is as the octavia-dashboard plugin requires it.

If so, we could probably make a special case where the requirements change for designate-dashboard would not cause major packaging/installer hardship.

If not, we will need to re-evaluate when a fix can be delivered due to the requirements change.

— Additional comment from Radomir Dopieralski on 2024-03-21 08:07:11 UTC —

[root@standalone ~]# podman exec -ti horizon /bin/bash
[root@standalone /]# rpm -qa | grep openstacksdk
python3-openstacksdk-0.55.0-0.20210316070305.964fec6.el8.noarch

— Additional comment from on 2024-03-29 09:55:11 UTC —

Hi Radomir

this is the output from customer controllers:

1. podman exec -ti horizon rpm -qa | grep openstacksdk
   python3-openstacksdk-0.55.1-17.1.20230621014133.f09ed4a.el9ost.noarch

— Additional comment from on 2024-04-02 15:19:45 UTC —

Hello, any update about it? Thanks

— Additional comment from Michael Johnson on 2024-04-11 20:01:58 UTC —

We have approval to make the requirements/RPM dependency changes to be able to backport this fix.
It will require changes in RDO and downstream backport. I am starting this work.
I will also clone this BZ to 18.x as upstream Antelope does not have this fix either due to the requirements change being against stable branch policy.