Last execution of cron-trigger doesn't work due to trust deletion

Bug #1708139 reported by Nikolay Makhotkin
22
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Mistral
Fix Released
Critical
Nikolay Makhotkin

Bug Description

Last cron-trigger execution deletes the trust but actions themselves don't work inside workflow execution:

[action_ex_id=df50ee04-c541-4c28-ac33-edfa5180687b, idx=0]: Failed to run action [action_ex_id=df50ee04-c541-4c28-ac33-edfa5180687b, action_cls='<class 'mistral.actions.action_factory.CinderAction'>', attributes='{u'client_method_name': u'volumes.list'}', params='{}']
 CinderAction.volumes.list failed: Authorization failed: Could not find trust: 7bca751a3abb4ecb9abe99f1e4f66c90 (HTTP 404) (Request-ID: req-71c09d7a-b232-4514-b812-4039887da9d7)

Changed in mistral:
status: Triaged → In Progress
Revision history for this message
Andras Kovi (akovi) wrote :
Revision history for this message
Andras Kovi (akovi) wrote :

(CORRECTED) A duplicate of this bug: https://bugs.launchpad.net/mistral/+bug/1699198

Revision history for this message
Nikolay Makhotkin (nmakhotkin) wrote :

Yes, exactly.

Changed in mistral:
milestone: pike-3 → pike-rc1
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to mistral (master)

Reviewed: https://review.openstack.org/490049
Committed: https://git.openstack.org/cgit/openstack/mistral/commit/?id=b8e16648ebd0a9a549d3eb49607672e412b3505c
Submitter: Jenkins
Branch: master

commit b8e16648ebd0a9a549d3eb49607672e412b3505c
Author: Nikolay Mahotkin <email address hidden>
Date: Wed Aug 2 17:46:34 2017 +0300

    [Trusts] Fix deleting trust

     * Delete trust only after the last execution of
       cron-trigger or event-trigger is completed.
       Otherwise during workflow execution we get
       an error "Unauthorized error: No such trust <id>"

    Closes-Bug: #1708139

    Change-Id: I42849d4f7c517f8a27e0d26c9cf0d98f9c7fb94a

Changed in mistral:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/mistral 5.0.0.0rc1

This issue was fixed in the openstack/mistral 5.0.0.0rc1 release candidate.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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