We're updating the issue view to help you get more done. 

Error when users try to update deployment with no new node types

Description

Problem:

Cloudify Manager returns a 500 error when existing deployment is updated with the same blueprint used to create it.

To reproduce:

cfy blueprints create -p <blueprint_1 archive> -n <blueprint_1 path> app_bp
cfy deployments create -b app_bp -i <inputs_1> app_dp
cfy executions start install -d app_dp
cfy deployments update -p <blueprint_1 archive> -n <blueprint_1 path> -i <inputs_2> app_dp

Expected Behavior:

As per the the documentation on http://docs.getcloudify.org/4.0.0/manager/update-deployment/ since there are no new node-types, Cloudify should return 200 and indicate to the user that nothing in the deployment has been updated

Steps to Reproduce

.

Why Propose Close?

None

Status

Assignee

Unassigned

Reporter

Anika Lindemann

Labels

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