Bug 1026412 - Horizon: Ordering by name doesn't work
Summary: Horizon: Ordering by name doesn't work
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: python-django-horizon
Version: 3.0
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
: 3.0
Assignee: Julie Pichon
QA Contact: Ami Jeain
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-11-04 15:16 UTC by Jaroslav Henner
Modified: 2015-02-15 22:02 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-07 12:08:13 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jaroslav Henner 2013-11-04 15:16:09 UTC
Description of problem:
There are lists that cannot be sorted by the column "name", including:
Snapshots: /dashboard/project/images_and_snapshots/
Summary: /dashboard/project/
Instances: /dashboard/project/instances/
...


Version-Release number of selected component (if applicable):
openstack-dashboard-2013.1.4-1.el6ost.noarch
python-django-horizon-2013.1.4-1.el6ost.noarch


How reproducible:
always

Steps to Reproduce:
1. Click on the ordering arrow. arrow
2.
3.

Actual results:
The arrow switches the orientation, but order remains the same. 

Expected results:
The arrow switches the orientation, list re-ordered by the column that have been clicked-on the last time.

Additional info:

Comment 2 Julie Pichon 2013-11-11 17:32:37 UTC
I can't reproduce using python-django-horizon-2013.1.4-1.el6ost.noarch.

I tried the /dashboard/project/images_and_snapshots/ and /dashboard/project/instances/ pages, and was able to sort by name in both cases (the arrow orientation changes, and the rows were reordered as expected). I'm using Firefox 22.0.

The ordering is handled in Javascript currently. Could you specify your browser and browser version? Did you encounter other Javascript errors? Does ordering by another column works? How many items are you trying to sort at once?

Thank you.

Comment 3 Julie Pichon 2013-11-19 10:45:48 UTC
Removing the 4.0 release target flags as this is marked as a 3.0 Regression. I cannot reproduce on RHOS 3.0 or 4.0 using Firefox or Chrome.

Comment 4 Jaroslav Henner 2013-12-09 09:23:06 UTC
(In reply to Julie Pichon from comment #2)
> I can't reproduce using python-django-horizon-2013.1.4-1.el6ost.noarch.
> 
> I tried the /dashboard/project/images_and_snapshots/ and
> /dashboard/project/instances/ pages, and was able to sort by name in both
> cases (the arrow orientation changes, and the rows were reordered as
> expected). I'm using Firefox 22.0.

Intereseting. It also cannot reproduce it now, except of the Floating IPs on:
/dashboard/project/access_and_security/

where with openstack-dashboard.noarch 2013.1.4-1.el6ost     @puddle (Grizzly)
The ordering by instance or IP seems to not work

On Havana, the ordering by IP seems to not work, but it seems to work on instances. It re-orders on first click, but after second click, it doesn't reverse the order.

Above has been done with ~25 Floating IPs.


Firefox 22.0. Inspecting with firebug, I have seen no Javascript errors. IIRC, mainly ordering by name was not working, strangely the other columns were working fine. I do not remember how many items I have been sorting.

> 
> The ordering is handled in Javascript currently. Could you specify your
> browser and browser version? Did you encounter other Javascript errors? Does
> ordering by another column works? How many items are you trying to sort at
> once?
> 
> Thank you.

Comment 5 Scott Lewis 2013-12-13 16:05:58 UTC
Adding regressions to next bugfix release

Comment 6 Julie Pichon 2014-01-07 12:08:13 UTC
Closing as it cannot be reproduced, per comments 3 and 4.

The issue with sorting Floating IPs is not a regression - it's a known problem that was fixed in Havana ( https://bugs.launchpad.net/horizon/+bug/1108085 ) but wasn't backported. If you noticed issues sorting floating IPs in Havana, please open a new bug for 4.0. Thanks!


Note You need to log in before you can comment on or make changes to this bug.