[Dashboard] ready to deploy env cannot be deployed

[Alex Kholkin]

Detailed bug description:
It is possible to create an env which will be ready to deploy but it will be impossible to deploy the env from Catalog > Environments in the Dashboard. There is no button "Deploy Environments"

Steps to reproduce:
1) In the Murano Dashboard go to > Applications > Catalog > Environments
2) create an env
3) add apach to the env and deploy it
4) after deployment delete apach from the env
5) go back to the Environments

Expected result:
it is possible to deploy the env

Actual result:
it is not possible to deploy the env(There is no button "Deploy Environments")

Reproducibility:
Always

Work around:
to update(deploy) env from the inside of the env

[Valerii Kovalchuk (vakovalchuk)]

Maybe it's not so medium, because we have quite easy workaround, and situation is not very common - usually you deploy env from its page after you delete its components

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/341030
Committed: https://git.openstack.org/cgit/openstack/murano-dashboard/commit/?id=c30ae0e06e5397141816e97bdd05dd3da35e7957
Submitter: Jenkins
Branch: master

commit c30ae0e06e5397141816e97bdd05dd3da35e7957
Author: Valerii Kovalchuk <email address hidden>
Date: Tue Jul 12 18:47:44 2016 +0300

    Fix allowance of Deploy environment action

    Previously action's allow() method didn't consider situation when
    component was deleted from deployed environment as the valid case
    to show the button. This patch fixes that by simply checking
    env's status to be 'pending' or 'deploy failure'.

    Change-Id: I40d62d4fcb620e7f2ffc515884c755abf6b8421c
    Closes-bug: #1594354

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/murano-dashboard 3.0.0.0b3 development milestone.