When a workflow is started with a source execution, the sourc execution should be added to the execution description
Bug #1762470 reported by
Dougal Matthews
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Fix Released
|
Low
|
Renat Akhmerov | ||
Bug Description
When starting an execution with "-s" option and providing a source execution ID, the ID should be added to the description of the execution object. This would then make it easier to recognise that an execution was started based on a previous one.
Both cron-triggers and sub-workflow executions do something similar by adding extra context and information to the executions.
The CLI command to start a workflow:
$ mistral execution-create -s [id-of-
The CLI command to check the execution description:
$ mistral execution-get [id-of-
| Changed in mistral: | |
| assignee: | nobody → Adriano Petrich (apetrich) |
| Changed in mistral: | |
| assignee: | Adriano Petrich (apetrich) → Renat Akhmerov (rakhmerov) |
| description: | updated |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to mistral (master) | #1 |
| Changed in mistral: | |
| status: | Confirmed → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mistral (master) | #2 |
| Changed in mistral: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/mistral 7.0.0.0b3 | #3 |
To post a comment you must log in.
Fix proposed to branch: master
Review: https:/