Status of the new app after adding it to the env with status "Deploy FAILURE" will be "Deploy FAILURE" also

[Alex Kholkin]

Detailed bug description:
After some deployment status of the env can be "Deploy FAILURE". If you are going to add a new app to a such env, status of this new app will be "Deploy FAILURE" also. But the status should be "ready to deploy" after adding an new app.

Steps to reproduce:
1) In the Murano Dashboard go to > Applications > Catalog > Environments
2) Create an env, add an app which will deploy with fail
3) Deploy this app
4) Check that status of the env is "Deploy FAILURE"
5) Add new app to this env
6) Check status of the new app

Expected result:
Status is "ready to deploy"

Actual result:
Status is "Deploy FAILURE"

Reproducibility:
Always

[Valerii Kovalchuk (vakovalchuk)]

Status of the each app in env is also the same as the status of the whole env. I'm not sure whether it is a bug or not, I guess it was made this way from the start

[Alex Kholkin (akholkin)]

Nope. If status was "Ready" and you will add a new app the status will be "Ready to deploy". If status was "Deploy FAILURE" and you will add a new app app the status will "Deploy FAILURE" instead of "Ready to deploy".

[Valerii Kovalchuk (vakovalchuk)]

I think it is opinionated. IMHO, adding new app to the failed env shouldn't mask the failure.