Deployment Update to Rollback DNW

Description

Deployment update works only once. Subsequent updates still fails with a 500 error, and then 409.

Here is the sequence of my test:

1. Install blueprint_v1.yaml – This worked. Apps in the blueprint get deployed/started.
2. Update from blueprint_v1.yaml à blueprint_v2.yaml – This worked. I changed a node name in the blueprint which resulted in the a node being removed/added.
3. Update from blueprint_v2.yaml à blueprint_v1.yaml – This didn’t work. I got a 500 error in return. This is supposed to roll the update in step 2 back to the state in step 1.
4. Update from blueprint_v2.yaml à blueprint_v1.yaml – This didn’t work. I got a 409 error in return. 409 is returned for subsequent update attempts.

The error returned in 409 indicates that there is already a deployment update active and provides execution ID. However, when listing executions on the manager, the execution ID does not exist in the manager.

Steps to Reproduce

.

Why Propose Close?

None

Status

Assignee

Unassigned

Reporter

Anika Lindemann

Labels

None

Severity

High

Target Version

4.4

Premium Only

no

Found In Version

4.2

QA Owner

Lital Hamami

Bug Type

None

Customer Encountered

None

Customer Name

None

Release Notes

yes

Priority

None

Sprint

None

Priority

Unprioritized
Configure