Category selector should cleanup page number to avoid error pages

[Timur Nurlygayanov]

Steps To Reproduce:
1. Upload several applications to Murano (for example, 10 applications) with different categories
2. Login to Horizon dashboard and navigate to Murano > Application Catalog > Applications
3. Click on 'Next' button
4. Select the custom category where we have no applications or have 1-2 applications only

Observed Result:
User will see the error message (please see attached screenshot) like:
The page you were looking for doesn't exist
You may have mistyped the address or the page may have moved.

The root of this problem in the following: When user clicks on 'Next' button, Horizon will add number of page to the end of the link, like:
https://dev-mox.manage.express.mirantis.com/dashboard/murano/catalog/index/Big%20Data/2
and if we will change the category after this, Horizon will not cleanup the page number and will try to open page 'N' for category which have no this page, in the result we will see 404 response code in the Horizon dashboard.

Need to fix this issue and cleanup the page number when user changes the category for filtering.

[Serg Melikyan (smelikyan)]

Timur, can you confirm this issue on MOS 6.0?

[Serg Melikyan (smelikyan)]

And on master version of Murano

[Serg Melikyan (smelikyan)]

I've nominated this issue to the corresponding series, please, confirm this issue on the "Incomplete" series.

[Victor Ryzhenkin (vryzhenkin)]

Can't reproduce on ISO:
{"build_id": "2014-12-18_01-32-01", "ostf_sha": "a9afb68710d809570460c29d6c3293219d3624d4", "build_number": "56", "auth_required": true, "api": "1.0", "nailgun_sha": "5f91157daa6798ff522ca9f6d34e7e135f150a90", "production": "docker", "fuelmain_sha": "45caacadb878abfbd9d60e134d72229698b469c9", "astute_sha": "16b252d93be6aaa73030b8100cf8c5ca6a970a91", "feature_groups": ["mirantis"], "release": "6.0", "release_versions": {"2014.2-6.0": {"VERSION": {"build_id": "2014-12-18_01-32-01", "ostf_sha": "a9afb68710d809570460c29d6c3293219d3624d4", "build_number": "56", "api": "1.0", "nailgun_sha": "5f91157daa6798ff522ca9f6d34e7e135f150a90", "production": "docker", "fuelmain_sha": "45caacadb878abfbd9d60e134d72229698b469c9", "astute_sha": "16b252d93be6aaa73030b8100cf8c5ca6a970a91", "feature_groups": ["mirantis"], "release": "6.0", "fuellib_sha": "73332192a257ea02c40a39885c502ad1ebdf3eda"}}}, "fuellib_sha": "73332192a257ea02c40a39885c502ad1ebdf3eda"}

[Serg Melikyan (smelikyan)]

This bug will be fixed in MOX in the next release, when MOX will move to the MOS 6.0