Orquesta workflow: Saving the definition again results in dup key error

[m4dcoder]

I modified the workflow metadata (try something different on the input parameter) and tried to save the workflow again. st2flow returns a DB error saying the workflow already exists.

[bmomberger-bitovi]

Saw this happen once but am having trouble replicating. @m4dcoder if you can replicate, please post the steps.

[LindsayHill]

Here's steps from Nick:

• Go to Actions tab

• Select a pack that you want to put your new workflow in
• Press the + button
• When EWC comes up, fill out the Name and Entry Point fields
• Click Save
• Edit the Description field
• Click Save
• Error Error saving workflow.: Tried to save duplicate unique keys (E11000 duplicate key error collection: st2.action_d_b index: uid_1 dup key: { : "action:default:nicktest3" })

Have not tested this myself

[blourdel]

I can replicate it relatively easily myself:

Select a pack that you want to put your new workflow in
Press the + button
When EWC comes up, fill out the Name and Entry Point fields
Click Save
Add a few actions and link them in a sequence
Click Save

Error saving workflow.: Tried to save duplicate unique keys (E11000 duplicate key error collection: st2.action_d_b index: uid_1 dup key: { : "action:training:sequence1" })

I can provide a system in a faulty state if needed.

[Kami]

This was fixed in v3.0.0, but not 100%.

There is still a race / edge case if you click save button twice in quick succession before workflow gets saved and actions re fetched. See #355 (comment) for details.

Which version are you using?

[blourdel]

I am using st2 3.0dev (2f5fa9b), on Python 2.7.12

Compared to #355 : in my case I did not act quickly and once you are in trouble the only workaround is to save under a different name.

[Kami]

It looks like you are using old version (2f5fa9b is 13 days old and doesn't include fixes we made for v3.0.0 mid to late last week (you can also confirm st2flow package version by doing dpkg -l |grep st2flow).

Please try upgrading - v3.0.0 stable is now out so you can directly upgrade to latest enterprise stable packages.