Bug 1238092
| Summary: | horizon hypervisor list not ordered alphabetically | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Eduard Barrera <ebarrera> |
| Component: | python-django-horizon | Assignee: | Itxaka <iserrano> |
| Status: | CLOSED ERRATA | QA Contact: | Ido Ovadia <iovadia> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | low | ||
| Version: | 6.0 (Juno) | CC: | aortega, athomas, iserrano, mrunge, rcernin, slong, srevivo |
| Target Milestone: | --- | Keywords: | Triaged, ZStream |
| Target Release: | 6.0 (Juno) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-django-horizon-2014.2.3-9.el7ost | Doc Type: | Bug Fix |
| Doc Text: |
Previously, under some circumstances, the hypervisor list was not alphabetized. In this update, the sort attribute has been changed, and badly sorted lists no longer occur.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2016-06-21 22:24:19 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: | |||
|
Description
Eduard Barrera
2015-07-01 08:01:11 UTC
It seems that on version 6 and 7, the hypervisor table was using a custom naturaSort parser in order to sort it, but it could give wrong results. This has been fixed on version 8. Did a backport upstream to 6 and 7: https://review.openstack.org/#/c/249661/ https://review.openstack.org/#/c/249664/ `2014.2.4 Juno EOL release has been pushed, all open stable/juno reviews will be abandoned.` So no backport upstream for version 6. Will cherry-pick the changes to 6 downstream. This bug was accidentally moved from POST to MODIFIED via an error in automation, please see mmccune with any questions Matthias, could you please do the doc text for this one, and I'll put it in the errata? thanks, Summer Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2016:1271 |