Application gets incorrect status after being added to failed environment

Bug #1441484 reported by Anastasia Kuznetsova
30
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Murano
Won't Fix
Medium
Unassigned
Mitaka
Won't Fix
Undecided
Unassigned
Newton
Confirmed
Medium
Unassigned

Bug Description

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

The root cause is the same as for https://bugs.launchpad.net/murano/+bug/1454723 bug

Revision history for this message
Anastasia Kuznetsova (akuznetsova) wrote :
Revision history for this message
Ekaterina Chernova (efedorova) wrote :

This bug relates to new design of environment statuses

Changed in murano:
status: New → Confirmed
milestone: none → liberty-1
importance: Undecided → High
importance: High → Medium
summary: - [ui] Application gets incorrect status after adding to failed
- environment
+ Application gets incorrect status after adding to failed environment
Changed in murano:
milestone: liberty-1 → liberty-2
Changed in murano:
milestone: liberty-2 → liberty-3
Changed in murano:
assignee: nobody → Nikolay Starodubtsev (starodubcevna)
assignee: Nikolay Starodubtsev (starodubcevna) → nobody
tags: added: api v2
Changed in murano:
milestone: liberty-3 → liberty-rc1
Changed in murano:
milestone: liberty-rc1 → ongoing
Changed in murano:
milestone: ongoing → next
tags: added: release-notes
description: updated
Changed in murano:
milestone: next → mitaka-1
Changed in murano:
importance: Medium → High
Changed in murano:
milestone: mitaka-1 → mitaka-2
Changed in murano:
milestone: mitaka-2 → mitaka-3
Changed in murano:
milestone: mitaka-3 → mitaka-rc1
Revision history for this message
Stan Lagun (slagun) wrote : Re: Application gets incorrect status after adding to failed environment

This is by current design and can be changed only by making major changes to API/deployment workflow => not a bug

Changed in murano:
status: Confirmed → Won't Fix
summary: - Application gets incorrect status after adding to failed environment
+ Application gets incorrect status after being added to failed
+ environment
no longer affects: murano/ocata
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.