Event filtering is non-obvious and broken
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Heat |
Triaged
|
Medium
|
Neetu Jain | ||
python-heatclient |
Invalid
|
Undecided
|
Unassigned |
Bug Description
To use the event filtering, you really need internal knowledge of the DB schema, because the filters don't align with the displayed columns, particularly for resource_status
E.g:
$ heat event-list overcloud -f "resource_
+----
| id | resource_
+----
+----
You have to specify it like this:
heat event-list overcloud -f "resource_
Which makes sense if you know the DB schema, but from a users perspective it's pretty mysterious..
Changed in heat: | |
assignee: | nobody → Satyanarayana Patibandla (satya-patibandla) |
summary: |
- Event filtering is non-obvious + Event filtering is non-obvious and broken |
tags: | added: tripleo |
Changed in heat: | |
status: | In Progress → Triaged |
assignee: | Steven Hardy (shardy) → nobody |
Changed in heat: | |
assignee: | nobody → Neetu Jain (nutshi) |
Changed in heat: | |
milestone: | none → no-priority-tag-bugs |
I've added heat, since I think this is a REST API issue rather than a client one.
There are 2 issues here: status= CREATE_ COMPLETE should work as expected
- resource_
- the API also needs to return separate attributes for status and action, and these should also be filterable