OpenStack Heat

event-list shows events in wrong order

Bug #1394376 reported by Clint Byrum
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Heat
Invalid
Medium
Unassigned

Bug Description

I believe we have regressed bug #1261883 by adding other pieces to the SQL query, which has accidentally led to not using the auto-increment ID as a sort key. This means we aren't getting events in insertion order anymore when calling event-list.

Revision history for this message
Qiming Teng (tengqim) wrote :

Is this happening only in a multiple stack (including nested stacks) scenario?

Anant Patil (ananta)
Changed in heat:
assignee: nobody → Anant Patil (ananta)
Anant Patil (ananta)
Changed in heat:
assignee: Anant Patil (ananta) → nobody
Revision history for this message
Angus Salkeld (asalkeld) wrote :

I was under the impression that the client now orders things correctly:
https://github.com/openstack/python-heatclient/commit/9b28902c5f949b29934aae7402fdb78e7088d7fe

Changed in heat:
status: Triaged → Incomplete
importance: High → Medium
Revision history for this message
Steve Baker (steve-stevebaker) wrote :

I've not seen event ordering issues for some time

Changed in heat:
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.