UI shows wrong status in Environments

Bug #1413260 reported by Natasha Beck
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Fix Released
Medium
Andrew Pashkin

Bug Description

When looking on the status in Environments-> components tab the status shows Deploy FAILURE although the latest status is Deployment History is success and the previous status was Failure.

Attached are the screen shots.

What caused this situation:
1. I uploaded a package where Mistral workflow is called during deployment.
2. I tried to deploy this package but it failed since Mistral workflow was not uploaded yet.
3. I uploaded the Mistral workflow and deployed again - this time successfully.
4. In the Deployment History I saw Successful, but in the status I still saw 'Deploy FAILURE' as you can see in the attached screen shots.

Revision history for this message
Natasha Beck (natabeck) wrote :
Revision history for this message
Ekaterina Chernova (efedorova) wrote :

Could you please add logs?

What did you change so the deployment finished successfully?

Changed in murano:
status: New → Incomplete
importance: Undecided → Medium
description: updated
Revision history for this message
Ekaterina Chernova (efedorova) wrote :

Andrew, please verify

Changed in murano:
assignee: nobody → Andrew Pashkin (apashkin)
status: Incomplete → New
Natasha Beck (natabeck)
description: updated
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to murano (master)

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

Changed in murano:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on murano (master)

Change abandoned by Andrew Pashkin (<email address hidden>) on branch: master
Review: https://review.openstack.org/154425

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (master)

Reviewed: https://review.openstack.org/154425
Committed: https://git.openstack.org/cgit/stackforge/murano/commit/?id=4ae29f2672ecf648591c3ab9317fcc694f063618
Submitter: Jenkins
Branch: master

commit 4ae29f2672ecf648591c3ab9317fcc694f063618
Author: Andrew Pashkin <email address hidden>
Date: Tue Feb 24 14:24:55 2015 +0300

    Fixed logic of determining environment status

    DEPLOYED status of sessions was not handled properly - the bug was
    caused that if environment was deployed with failure it may remain with
    this status even if it was deployed successfully after that.

    Change-Id: I00309a7605067727eca4108e3fedac7bf0998847
    Closes-Bug: #1413260

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