Lack of pagination on recordset page

the same error occurs when listing zones. It always displays only the max. 20 items, all subsequent skips and the next button does not appear

Same here: only 20 records are accessible.

Same bug here on PIKE

So it seems the dashboard is lacking the ability to handle the chunked response it receives from the API. Compare this function that is being used in the python client

https://github.com/openstack/python-designateclient/blob/master/designateclient/v2/utils.py#L57

vs. the simplistic function in the dashboard

https://git.openstack.org/cgit/openstack/designate-dashboard/tree/designatedashboard/static/designatedashboard/resources/os-designate-recordset/api.service.js#n64

Hi,

May i know the status of this?

This bug is still open, I did try to resolve it, but failed due to lack of understanding javascript and the frameworks that are involved.

Hi,

as has been noted before, designateclient supports loading data from multiple API
pages (see links above). Is there a reason why the ng version of designate-dashboard
doesn't use the client, opting instead to query the designate API directly?

Hi,

just increase default_limit_v2 from defaults in designate.conf and You will get pages in recordset

@Marek: I don't think there is a specific reason, if you can rewrite the code to use the designateclient and solve this issue, that would be very welcome.

Given that the client support the pagination, increasing the limit of each page in designate appears to be a workaround and this bug seems to be valid

100% a bug should look like the other things inside horizon with pagination.

I ran into this issue on Ussuri. Is there any chance this might be picked up and fixed by anyone?
Or would anybody accept and review a patchset?

Has there been any progress on this? Is anyone working on this currently?

Hi guys, just like Zara and Christian I would be interested to know if anyone is currently working on this bug.

Seems there isn't any visible progress at least, feel free to take over. If you submit a patch, best join #openstack-dns on OFTC so we can chat about it.

We experienced same issue. We solved it by adding

[service:api]
default_limit_v2 =

to designate.conf. Empty value menas None and it causes that designate will send all results at once without pagination.

This bug has been reported for a long time, is no one working on this?

Hi, is there any update on this?