Mistral wf stuck in RUNNING if the sum of task's output is more than limit

Bug #1796592 reported by Oleg Ovcharuk
This bug affects 1 person
Affects Status Importance Assigned to Milestone
In Progress
Oleg Ovcharuk

Bug Description

If each task's published output is fit in execution_field_size_limit_kb, but the sum of them is not, mistral's workflow could stuck in RUNNING state.

Look at this example:

execution_field_size_limit_kb = 500

      action: std.http
        url: <% "https://en.wikipedia.org/wiki/QWERTY" %>
        out1: <% task().result %>
      action: std.http
        url: <% "https://en.wikipedia.org/wiki/QWERTY" %>
        out2: <% task().result %>

size(out1) == size(out2) == ~ 400 KB
but wf's output, which includes both out1 and out2 is bigger than 500KB limit.

expected result: there is error message in logs and workflow's state is ERROR
actual result: there is error message in logs, but workflow's state stuck in RUNNING

Changed in mistral:
assignee: nobody → Oleg Ovcharuk (vgvoleg)
milestone: none → stein-1
importance: Undecided → High
status: New → Confirmed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to mistral (master)

Fix proposed to branch: master
Review: https://review.openstack.org/608469

Changed in mistral:
status: Confirmed → In Progress
Dougal Matthews (d0ugal)
Changed in mistral:
milestone: stein-1 → stein-2
Changed in mistral:
milestone: stein-2 → stein-3
Changed in mistral:
milestone: stein-3 → train-1
Changed in mistral:
milestone: train-1 → ussuri-1
Changed in mistral:
milestone: ussuri-1 → ussuri-2
Changed in mistral:
milestone: ussuri-2 → ussuri-3
Changed in mistral:
milestone: ussuri-3 → ussuri-rc1
Changed in mistral:
milestone: ussuri-rc1 → victoria-1
Changed in mistral:
milestone: victoria-1 → wallaby-1
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.