Murano

Murano instances don't get fl ips after redeploy of Murano env (if it fails with StackValidationError during first deployment)

Bug #1482217 reported by Anastasia Kuznetsova
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Fix Released
High
Stan Lagun
Murano 1.0.1
Kilo
Fix Committed
High
Stan Lagun
Murano 2015.1.1
Liberty
Fix Released
High
Stan Lagun
Murano 1.0.1

Bug Description

Steps to reproduce:
1. Create Murano environment
2. Add simple app to the env (e.g. Tomcat), select "Assign Floating IP", select "m1.medium"
3. Navigate to "Project" > "Admin" > "Flavors"
4. Rename "m1.medium" to "m1.medium111"
5. Come back to "Murano" > "Application Catalog" > "Environments"
5. Send created env to deploy, deploy should fail with error: [heatclient.exc.HTTPBadRequest]: ERROR: Property error
6. Navigate to "Project" > "Admin" > "Flavors", rename "m1.medium111" to "m1.medium"
7. Naviagte to "Murano" > "Environments"
8. Send the same environment to deploy

Actual result:
Second deployment of Murano environment has "Success" status, but instance with Murano app has no floating IP
In last operation we can see Tomcat is available at http://None

Anastasia Kuznetsova (akuznetsova)
Changed in murano:
importance: Undecided → High
Serg Melikyan (smelikyan)
Changed in murano:
assignee: nobody → Stan Lagun (slagun)
Kirill Zaitsev (kzaitsev)
tags: added: engine kilo-backport-potential
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to murano (master)

Fix proposed to branch: master
Review: https://review.openstack.org/210077

Changed in murano:
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to murano (stable/kilo)

Fix proposed to branch: stable/kilo
Review: https://review.openstack.org/210078

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (master)

Reviewed: https://review.openstack.org/210077
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=a2db2eee39e78323bad607cc86b849d19db5141c
Submitter: Jenkins
Branch: master

commit a2db2eee39e78323bad607cc86b849d19db5141c
Author: Stan Lagun <email address hidden>
Date: Thu Aug 6 21:35:51 2015 +0300

    Postpone setting fipAssigned attribute until stack successful push

    Instance class set fipAssigned attribute attribute indicating that it has
    assigned floating IP address prior to stack.push() if then stack push
    failed on a subsequent deployments Instance didn't tried to allocate
    FIP again

    Change-Id: Ic467d7f4dc3b248c4f8f55be7997a4d2d90924a3
    Closes-Bug: #1482217

Changed in murano:
status: In Progress → Fix Committed
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (stable/kilo)

Reviewed: https://review.openstack.org/210078
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=4e55430d5d544a951b2c318f53b2c05880792123
Submitter: Jenkins
Branch: stable/kilo

commit 4e55430d5d544a951b2c318f53b2c05880792123
Author: Stan Lagun <email address hidden>
Date: Thu Aug 6 21:35:51 2015 +0300

    Postpone setting fipAssigned attribute until stack successful push

    Instance class set fipAssigned attribute attribute indicating that it has
    assigned floating IP address prior to stack.push() if then stack push
    failed on a subsequent deployments Instance didn't tried to allocate
    FIP again

    Change-Id: Ic467d7f4dc3b248c4f8f55be7997a4d2d90924a3
    Closes-Bug: #1482217

Serg Melikyan (smelikyan)
Changed in murano:
status: Fix Committed → Fix Released
Serg Melikyan (smelikyan)
Changed in murano:
milestone: liberty-3 → 1.0.0
Kirill Zaitsev (kzaitsev)
Changed in murano:
milestone: 1.0.0 → 1.0.1
Revision history for this message
Doug Hellmann (doug-hellmann) wrote : Fix included in openstack/murano 2015.1.1

This issue was fixed in the openstack/murano 2015.1.1 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

This issue was fixed in the openstack/murano 2015.1.1 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.