Bug 1481144
| Summary: | Events are displayed in wrong order, latest on the bottom | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [oVirt] ovirt-engine | Reporter: | Petr Matyáš <pmatyas> | ||||
| Component: | Frontend.WebAdmin | Assignee: | Alexander Wels <awels> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Petr Matyáš <pmatyas> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 4.1.5.2 | CC: | astepano, bugs, gshereme, knarra, mburman | ||||
| Target Milestone: | ovirt-4.1.6 | Keywords: | Reopened | ||||
| Target Release: | --- | Flags: | rule-engine:
ovirt-4.1+
|
||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: |
Cause: A regression bug caused system events to be sorted chronologically, earliest events at the top.
Fix: Events are now properly sorted, latest at the top.
|
Story Points: | --- | ||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-09-19 10:01:31 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | UX | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Petr Matyáš
2017-08-14 08:28:10 UTC
*** Bug 1484043 has been marked as a duplicate of this bug. *** Looks the same as Bug 1478687, assigning to infra (In reply to Greg Sheremeta from comment #2) > Looks the same as Bug 1478687, assigning to infra It is the same, this one is just for 4.1, not 4.2. *** This bug has been marked as a duplicate of bug 1486513 *** Duplicate is not relevant. This bug is about wrong order of events but bug marked as duplicated is about refresh of events tab. It's the same problem. You just don't see the new events because of the incorrect sort. Well to be fair, this bug is older than the duplicate, so the it can't be a duplicate since the bug marked as duplicate didn't exist at the time this was created. BZ 1478687 and this report are the same issue(and it doesn't matter who is duplicated on who), in the bottom line it's the same bug. Exactly, so lets close your bug, as mine has better description as is older. As you can see QA contact could make heads or tails from your description. *** Bug 1486135 has been marked as a duplicate of this bug. *** Verified on ovirt-engine-4.1.6.2-0.1.el7.noarch |