[murano] Application get incorrect status after adding to failed environment

[Anastasia Kuznetsova]

Steps to reproduce:
1. Log in Web UI
2. Navigate to Murano > Manage > Package Definitions
3. Import package
4. Navigate to Murano > Application Catalog > Environment
5. Create environment and add application to it
6. Send to deploy created environment and during deploy delete application instance
7. After deployment failure add one more application to it
8. Take a look at added application status

Bug in upstream https://bugs.launchpad.net/murano/+bug/1441484

[Ekaterina Chernova (efedorova)]

Sorry, it's by design.

For now we are not planning to change this behavior.

[Ekaterina Chernova (efedorova)]

Release notes:

If deployemtn of environment get failed, and new app is added to the same environment it would have faild state also, but actually it's not deploed yet. Real status will be provided after perssing 'Deply environment' button. (after env will send to deploy)

It happend because new applicaion status is equal to status of the whole environemnt. So if the deployment was sucesful, new app will have Ready status, but again it's not deployed

[Ekaterina Chernova (efedorova)]

Bug in upstream is not going to be fixed until 7.0 release

[Ekaterina Chernova (efedorova)]

After all investigations we find out that is bug can not be fixed separately. It only can be fixed as part of new API: https://blueprints.launchpad.net/murano/+spec/api-vnext

So if this feature would be accepted for the next versions this bug will be fixes automatically