A task should not be called 'fail', 'succeed', 'pause', 'noop'
Bug #1705186 reported by
Xavier Hardy
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Fix Released
|
Medium
|
Hardik Jasani | ||
Bug Description
It should not be possible to call a task `fail` since `fail` has become a keyword to trigger a workflow failure.
For instance, this will not call the task called `fail` but fail immediatly after init has been called.
```
version: '2.0'
the.bug:
type: direct
output:
test_value: <% $.value %>
tasks:
init:
- fail
fail:
action: std.fail
```
| summary: |
- A task should not be called 'fail' + A task should not be called 'fail', 'succeed', 'pause', 'noop' |
| Changed in mistral: | |
| milestone: | none → queens-1 |
| importance: | Undecided → Medium |
| assignee: | nobody → noa (noa-koffman) |
Revision history for this message
| Renat Akhmerov (rakhmerov) wrote | #1 |
| Changed in mistral: | |
| milestone: | queens-1 → queens-2 |
| Changed in mistral: | |
| milestone: | queens-2 → queens-3 |
| Changed in mistral: | |
| assignee: | noa (noa-koffman) → Hardik Jasani (hjasani) |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix proposed to mistral (master) | #2 |
| Changed in mistral: | |
| status: | New → In Progress |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mistral (master) | #3 |
| Changed in mistral: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/mistral 6.0.0.0b3 | #4 |
To post a comment you must log in.
The same about "succeed", "pause" and "noop". They are also language keywords that are reserved for specific engine commands that change a workflow execution state directly.