Update command for nonexistent element works different for different Mistral items
Bug #1418545 reported by
Anastasia Kuznetsova
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Mistral |
Fix Released
|
Low
|
Limor Stotland | ||
| Liberty |
Fix Released
|
Low
|
Limor Stotland | ||
Bug Description
Need to be consistent in implementation of update method.
For example if we take a look at workflows, we will see that we can execute workflow-update if there is no such wf, it will be created:
https:/
Another situation with workbooks and environments:
https:/
https:/
| Changed in mistral: | |
| importance: | Undecided → Low |
| milestone: | none → kilo-3 |
| status: | New → Incomplete |
| status: | Incomplete → New |
| no longer affects: | mistral/kilo |
| Changed in mistral: | |
| assignee: | nobody → Limor Stotland (limor-bortman) |
| Changed in mistral: | |
| status: | New → In Progress |
Revision history for this message
| Limor Stotland (limor-bortman) wrote | #1 |
| description: | updated |
| description: | updated |
Revision history for this message
| Renat Akhmerov (rakhmerov) wrote | #2 |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to mistral (master) | #3 |
| Changed in mistral: | |
| status: | In Progress → Fix Committed |
| Changed in mistral: | |
| milestone: | 1.0.0 → none |
To post a comment you must log in.
I propose a fix but for some reason it's not connect to the bug :
https:/