New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Node List - Fails to display greater than 100 nodes per page #2514

Closed
JustinAddams opened this Issue May 16, 2017 · 2 comments

Comments

Projects
None yet
2 participants
@JustinAddams

Issue type: Bug report

My Rundeck detail

  • Rundeck version: 2.8.2
  • Install type: RPM
  • OS Name/version: CentOS 7
  • DB Type/version: postgres

Expected Behavior
On the node list page my filter returns greater than 20 results, in this case 665. I want to view more nodes per page so I change the per page value to a higher value and see that many results per page.

Actual Behavior
On changing the Per Page value to any value greater than 100, the page refreshes successfully but still only displays 100 results.

How to reproduce Behavior
Change the Per Page value to any number greater than 100.

Further Info
Is there a log I can look in to grab errors around this page generation to assist in troubleshooting?
My node list is generated from a Script, configured in Project Settings, Resource Format = JSON

@JustinAddams

This comment has been minimized.

Show comment
Hide comment
@JustinAddams

JustinAddams Jul 6, 2017

Just rebuilt my Rundeck setup onto a MSSQL database backend and the same issue occurs, unsure if this info will help.

Just rebuilt my Rundeck setup onto a MSSQL database backend and the same issue occurs, unsure if this info will help.

@gschueler gschueler added the bug label Jul 6, 2017

@gschueler

This comment has been minimized.

Show comment
Hide comment
@gschueler

gschueler Jul 6, 2017

Member

there is an internal truncation value of 100, meant to be used when the node results are displayed e.g. in a widget like in the job editor page. Sounds like the internal truncation is happening even if the paging size is greater than that. The fix would be to not truncate results if paging size is greater than the truncation size

Member

gschueler commented Jul 6, 2017

there is an internal truncation value of 100, meant to be used when the node results are displayed e.g. in a widget like in the job editor page. Sounds like the internal truncation is happening even if the paging size is greater than that. The fix would be to not truncate results if paging size is greater than the truncation size

@gschueler gschueler added this to the 2.8.4 milestone Jul 6, 2017

@gschueler gschueler closed this in a1bcb57 Jul 12, 2017

gschueler added a commit that referenced this issue Jul 12, 2017

Merge pull request #2619 from rundeck/issue/2514
Fix #2514 don't truncate node results at 100 in node listing
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment