Activity log for bug #1792975

Date Who What changed Old value New value Message
2018-09-17 15:49:46 Oleg Ovcharuk bug added bug
2018-09-17 15:52:59 Oleg Ovcharuk summary Mistral saves wrong wf definition in case of creating multiple wf Mistral saves whole yaml for every wf definition in case of creating multiple wf.
2018-09-17 15:56:28 Oleg Ovcharuk description Whenever we want to save multiple wf from one yaml, every saved wf will have all this input in their definitions. This behavior doesn't match with saving one wf. This could be bad for users, who want to parse definition. Whenever we want to save multiple wf from one yaml, every saved wf will have all this input in their definitions. This behavior doesn't match with saving one wf. This could be bad for users, who want to parse definition. For example: I want to create two workflows from file wfs.yaml """ version: '2.0' wf1: type: direct tasks: task1: action: std.noop wf2: type: direct tasks: task1: action: std.noop """ mistral workflow-get-definition wf1 Expected output: """ version: '2.0' wf1: type: direct tasks: task1: action: std.noop """ Actual output: """ version: '2.0' wf1: type: direct tasks: task1: action: std.noop wf2: type: direct tasks: task1: action: std.noop """ The same behavior appears when I want to update wfs.
2018-09-17 17:01:03 Vitalii Solodilov mistral: milestone stein-1
2018-09-17 17:01:07 Vitalii Solodilov mistral: importance Undecided Medium
2018-09-17 17:01:36 Vitalii Solodilov mistral: assignee Oleg Ovcharuk (vgvoleg)
2018-09-17 17:01:42 Vitalii Solodilov mistral: status New Confirmed
2018-09-17 18:53:35 OpenStack Infra mistral: status Confirmed In Progress
2018-11-12 10:45:09 OpenStack Infra mistral: status In Progress Fix Released