Workflow fails to publish UI logs

Bug #1803724 reported by Honza Pokorny
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
tripleo
Fix Released
High
Honza Pokorny

Bug Description

Failed to handle action completion [error=Can not evaluate YAQL expression [expression=task().result.select($._id), error=u'_id', data={}]

(undercloud) [stack@undercloud-0 ~]$ openstack workflow execution output show c25f375e-116f-42a1-b561-5e64006e1811
{
    "result": "Failed to handle action completion [error=Can not evaluate YAQL expression [expression=task().result.select($._id), error=u'_id', data={}], wf=tripleo.plan_management.v1.publish_ui_logs_to_swift, task=get_messages, action=zaqar.claim_messages]:\nTraceback (most recent call last):\n File \"/usr/lib/python2.7/site-packages/mistral/engine/task_handler.py\", line 110, in _on_action_complete\n task.on_action_complete(action_ex)\n File \"/usr/lib/python2.7/site-packages/osprofiler/profiler.py\", line 159, in wrapper\n result = f(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/mistral/engine/tasks.py\", line 381, in on_action_complete\n self.complete(state, state_info)\n File \"/usr/lib/python2.7/site-packages/osprofiler/profiler.py\", line 159, in wrapper\n result = f(*args, **kwargs)\n File \"/usr/lib/python2.7/site-packages/mistral/engine/tasks.py\", line 221, in complete\n data_flow.publish_variables(self.task_ex, self.task_spec)\n File \"/usr/lib/python2.7/site-packages/mistral/workflow/data_flow.py\", line 215, in publish_variables\n task_ex.published = expr.evaluate_recursively(branch_vars, expr_ctx)\n File \"/usr/lib/python2.7/site-packages/mistral/expressions/__init__.py\", line 100, in evaluate_recursively\n data[key] = _evaluate_item(data[key], context)\n File \"/usr/lib/python2.7/site-packages/mistral/expressions/__init__.py\", line 79, in _evaluate_item\n return evaluate(item, context)\n File \"/usr/lib/python2.7/site-packages/mistral/expressions/__init__.py\", line 71, in evaluate\n return evaluator.evaluate(expression, context)\n File \"/usr/lib/python2.7/site-packages/mistral/expressions/yaql_expression.py\", line 159, in evaluate\n cls).evaluate(trim_expr, data_context)\n File \"/usr/lib/python2.7/site-packages/mistral/expressions/yaql_expression.py\", line 113, in evaluate\n \", data=%s]\" % (expression, str(e), data_context)\nYaqlEvaluationException: Can not evaluate YAQL expression [expression=task().result.select($._id), error=u'_id', data={}]\n"
}

Changed in tripleo:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (master)

Reviewed: https://review.openstack.org/618535
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=9198805df845816f21a9041e4c8cac98f42e4863
Submitter: Zuul
Branch: master

commit 9198805df845816f21a9041e4c8cac98f42e4863
Author: Honza Pokorny <email address hidden>
Date: Fri Nov 16 10:53:54 2018 -0400

    Select message IDs properly when publishing to swift

    Zaqar messages used to have their IDs under the "_id" key. This has
    been changed to "id". We're updating the select() call to reflect that.

    Change-Id: I2bf66ece33306178c36b51f82c9d16663743d660
    Partial-Bug: 1803724

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.openstack.org/618572
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=7c960d0bc06ebc4dd70bb4b1563b5d20d69cc356
Submitter: Zuul
Branch: master

commit 7c960d0bc06ebc4dd70bb4b1563b5d20d69cc356
Author: Honza Pokorny <email address hidden>
Date: Fri Nov 16 13:47:08 2018 -0400

    Exit when container is missing or empty when downloading logs

    The workflow should exit early if the logging container isn't present or
    is empty. In that case, there aren't any logs to hand back to the
    client so we're going to tell them that and fail.

    Change-Id: I10747b593f8c5d4c81ae737e8bd279f8b312559c
    Partial-Bug: 1803724

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to tripleo-common (stable/rocky)

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/619249

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Fix proposed to branch: stable/rocky
Review: https://review.openstack.org/619250

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to tripleo-common (stable/rocky)

Reviewed: https://review.openstack.org/619249
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=d8f06646ff3b99e8e9e31a1319bd253cf991d3ea
Submitter: Zuul
Branch: stable/rocky

commit d8f06646ff3b99e8e9e31a1319bd253cf991d3ea
Author: Honza Pokorny <email address hidden>
Date: Fri Nov 16 10:53:54 2018 -0400

    Select message IDs properly when publishing to swift

    Zaqar messages used to have their IDs under the "_id" key. This has
    been changed to "id". We're updating the select() call to reflect that.

    Change-Id: I2bf66ece33306178c36b51f82c9d16663743d660
    Partial-Bug: 1803724
    (cherry picked from commit 9198805df845816f21a9041e4c8cac98f42e4863)

tags: added: in-stable-rocky
Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

Reviewed: https://review.openstack.org/619250
Committed: https://git.openstack.org/cgit/openstack/tripleo-common/commit/?id=b45a5cee6ba2650d4e2d1211cd2975dc8f92a6c8
Submitter: Zuul
Branch: stable/rocky

commit b45a5cee6ba2650d4e2d1211cd2975dc8f92a6c8
Author: Honza Pokorny <email address hidden>
Date: Fri Nov 16 13:47:08 2018 -0400

    Exit when container is missing or empty when downloading logs

    The workflow should exit early if the logging container isn't present or
    is empty. In that case, there aren't any logs to hand back to the
    client so we're going to tell them that and fail.

    Change-Id: I10747b593f8c5d4c81ae737e8bd279f8b312559c
    Partial-Bug: 1803724
    (cherry picked from commit 7c960d0bc06ebc4dd70bb4b1563b5d20d69cc356)

Changed in tripleo:
status: In Progress → Fix Released
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.