MessagingTimeout when run-action is used to run another action

Bug #1656862 reported by Dawid Deja
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Mistral
Triaged
Medium
Unassigned

Bug Description

When 'mistral run-action' is used to run another action/workflow it leads to cycle call (engine is calling executor which then calls engine) which results in deadlock.

Changed in mistral:
status: New → Confirmed
assignee: nobody → Dawid Deja (dawid-deja-0)
Dougal Matthews (d0ugal)
Changed in mistral:
status: Confirmed → Triaged
importance: Undecided → Medium
assignee: Dawid Deja (dawid-deja-0) → nobody
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.