Inventory list needs to reset offset when paging limit increased

[cdcabrera]

Description

Appears to be a bug, the offset/page doesn't reset when the paging limit is increased. this can lead to an API 4XX level error

Expected behavior

The GUI shouldn't break when increasing the paging limit.

Steps to reproduce

1. Locate an account with over 10 inventory listings
2. navigate to the 2nd offset/page with the paging controls
3. select to increase the paging display limit
4. error should be throw and the GUI displays an error state

Additional context, version info

• 1/2 of the remaining UI/UX blocking for Development for an inventory listing #10
• 2/2 see Show clusters in openshift based on sockets and cores #383

[ntkathole]

Good catch @cdcabrera

[cdcabrera]

@ntkathole if you could also confirm this has been resolved before we close this one down, that would be awesome!

[ntkathole]

@cdcabrera This is still an issue. We should also reset offset when new filter applied. Here are steps:

1. Have 100+ RHEL hosts and out of which only around 20 are "premium".
2. Navigate to RHEL page.
3. Navigate to last page of system table.
4. Select SLA filter "Premium".

[cdcabrera]

@ntkathole updates around reseting the paging when manipulating filters should be in CI-beta when you're available to confirm

[ntkathole]

@cdcabrera There is still issue for openshift cores/socket filter. Here are steps:

1. Have openshift clusters based on sockets less than openshift clusters based on cores.
2. Navigate to openshift page.
3. Navigate to last page of system table.
4. Select "sockets" in filter.

[cdcabrera]

Looks like we need a better way of handling this, investigating something a little bit more centralized so when we add additional filters we don't need to update multiple locations of paging resets.

[cdcabrera]

Third round for the win, I hope =)

@ntkathole updates around reseting the paging when manipulating filters should be in CI-beta when you're available to confirm

We'll be squashing the last 3 #400 bug fix commits down into a single commit after confirmation, and doing the same for the #383 commits so we can track them a bit easier

[ntkathole]

@cdcabrera Issue is fixed now. Thank you 🎉