Image pagination in Horizon works wrong

[Yury Tregubov]

During Horizon UI tests of MOS8.0 ISO 589 the following behaviour was found.

As precondition 'Images per page' is set to 1, and there are 4 images available in project.
So each image will be displayed on separate page.

Then we check the 'Next' button. It works well.
After each click the next expected page is displayed.

But the 'Prev' button always leads to the first page.
If it is clicked on the third or forth page the very first page is opened.

The same scenario was checked in upstream and there is no such problem.

[Roman Podoliaka (rpodolyaka)]

No longer fixing Medium bugs in 8.0, closing as Won't Fix.

MOS Horizon team, please give it a try in 9.0.

[Timur Sufiev (tsufiev-x)]

Actually this bug was fixed here https://review.openstack.org/#/c/130844/21/openstack_dashboard/dashboards/project/images/views.py - the commit is already merged, so we should have it in Mitaka.

[Sergii Turivnyi (sturivnyi)]

Was tested on 9.0
Description in related bugs
https://bugs.launchpad.net/mos/+bug/1557078
https://bugs.launchpad.net/mos/+bug/1557065
https://bugs.launchpad.net/mos/+bug/1557056

[Timur Sufiev (tsufiev-x)]

Sergii, your last comments seems misleading to me. Were you actually testing Images pagination? Was the observed behavior the same as Yury had described?

How could it be related to Volume Snapshots pagination and displaying of different Volume tabs (left alone the bug about how cookies are shared between browsers). These 4 bugs look completely irrelevant to me.

[Timur Sufiev (tsufiev-x)]

Just reverified the bug on

[Timur Sufiev (tsufiev-x)]

* Just reverified the bug on env ^^^, if Image is being created with 'Public' flag checked, it appears in Images table (both Admin and Project), and pagination there works fine. We already have a separate bug for private Images not shown in Project->Images, see https://bugs.launchpad.net/mos/+bug/1551245

Sergii, could you please confirm that this bug is fixed?

[Dina Belova (dbelova)]

Added move-to-10.0 tag due to the fact bug was transferred from 9.0 to 10.0

[Roman Podoliaka (rpodolyaka)]

Closing as Invalid after a month without feedback.