deploy workflow executions aren't visible via mistral CLI

[Steven Hardy]

I had a deploy fail, but the status is SUCCESS, so I need to debug the individual executions to figure out what went wrong running the workflow, but it seems the data is either hidden or not recorded by mistral, e.g:

(undercloud) [stack@undercloud ~]$ openstack workflow execution show 28673f6c-d6ce-414c-ae7b-fcb28aa842af
+--------------------+--------------------------------------+
| Field | Value |
+--------------------+--------------------------------------+
| ID | 28673f6c-d6ce-414c-ae7b-fcb28aa842af |
| Workflow ID | 000abed5-20c2-4d18-84e2-7c982addb552 |
| Workflow name | tripleo.deployment.v1.deploy_plan |
| Workflow namespace | |
| Description | |
| Task Execution ID | <none> |
| State | SUCCESS |
| State info | None |
| Created at | 2018-03-16 13:49:17 |
| Updated at | 2018-03-16 13:50:30 |
+--------------------+--------------------------------------+
(undercloud) [stack@undercloud ~]$ openstack workflow execution list | grep 28673f6c-d6ce-414c-ae7b-fcb28aa842af
(undercloud) [stack@undercloud ~]$ openstack action execution list | grep tripleo.deployment.v1.deploy_plan
(undercloud) [stack@undercloud ~]$

Looking in the DB it seems we do have a record for the workflow execution, but no action executions at all associated with the workflow execution ID:

MariaDB [mistral]> select * from workflow_executions_v2 where id like '28673f6c-d6ce-414c-ae7b-fcb28aa842af';
...
1 row in set (0.00 sec)

MariaDB [mistral]> select * from action_executions_v2 where workflow_id like '28673f6c-d6ce-414c-ae7b-fcb28aa842af';
Empty set (0.27 sec)

So this is inconsistent with the CLI which doesn't list this record in workflow execution list.

I'm not sure how you can debug a failing workflow with this information ommitted, particularly the task execution so you can reconstruct the graph and figure out why the output wasn't as expected?

[Dougal Matthews (d0ugal)]

Are you looking for this? I think it might give you the output you want?

    openstack action execution list 28673f6c-d6ce-414c-ae7b-fcb28aa842af

When debugging I usually use these commands (I tend to prefer the shorter non-openstack commands)

mistral execution-list
mistral execution-get
mistral task-list
mistral action-exection-list

[Dougal Matthews (d0ugal)]

It is also worth noting that the task-list and action-execution-list are paginated (but exection-list isn't, because reasons). They will only show the first 100 by default

[Dougal Matthews (d0ugal)]

I believe this didn't show up due to the pagination, and thus isn't a bug in Mistral. It is best to filter with the Mistral API or CLI args rather than grep.

[Marios Andreou (marios-b)]

This is an automated action. Bug status has been set to 'Incomplete' and target milestone has been removed due to inactivity. If you disagree please re-set these values and reach out to us on freenode #tripleo

[Launchpad Janitor (janitor)]

[Expired for tripleo because there has been no activity for 60 days.]