Bug 1292734
| Summary: | When sorting by instance size, it's not sorted the right way | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Matthias Runge <mrunge> |
| Component: | python-django-horizon | Assignee: | Radomir Dopieralski <rdopiera> |
| Status: | CLOSED NOTABUG | QA Contact: | Ola Pavlenko <opavlenk> |
| Severity: | low | Docs Contact: | |
| Priority: | medium | ||
| Version: | 7.0 (Kilo) | CC: | aortega, athomas, beth.white, dhill, iovadia, mrunge, srevivo |
| Target Milestone: | --- | Keywords: | TestOnly, Triaged, ZStream |
| Target Release: | 7.0 (Kilo) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-django-horizon-2015.1.3-1.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Cause:
Sorting of flavors doesn't make sense
Consequence:
Fix:
Sorting was removed from flavor column
Result:
Horizon does not provide the false claim any more, that sorting by flavor makes any sense.
|
Story Points: | --- |
| Clone Of: | 1262107 | Environment: | |
| Last Closed: | 2017-06-29 14:11:22 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
| Bug Depends On: | 1262107 | ||
| Bug Blocks: | |||
|
Comment 1
Matthias Runge
2016-06-14 07:31:12 UTC
According to our records, this should be resolved by python-django-horizon-2015.1.4-1.el7ost. This build is available now. Failed QA ========= Failed on: python-django-horizon-2015.1.4-1.el7ost.noarch How Reproduced: =============== 1. Create many instances of different size (flavors) 2. Go to (http://public_vip/dashboard/project/instances/) 3. Play with the "Size" column sorting until you notice the sorting failure Actual results: =============== Instances don't sort, it seems that the sorting is missing on this column Expected results: ================= Instances sort by size ============================================== Test 2: ======= 1. Create many instances of different size (flavors) 2. Go to (http://public_vip/dashboard/admin/instances/) 3. Play with the "Size" column sorting until you notice the sorting failure Actual results: =============== m1.tiny m1.tiny m1.tiny m1.medium m1.small Expected results: ================= m1.tiny m1.tiny m1.tiny m1.small m1.medium That's actually the issue with this bug. No sorting makes sense here, there are way too many variables (cpu, ram, disk, ...) It shouldn't be sortable. if it is, that's actually the bug. In my tests, in projects/instances, the size attribute is not sortable. As above comment, the flavor column is not sortable due to the number of variables involved. This table does not have a size column. |