Murano reads wrong heat stack output and doesn't identify FIP in case of nova-network

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

Bug Description

If user has "nova-network" instead of "neutron" then after successful deployment of murano application user sees following message in deployment logs:
<Application> is available at http://None

while heat reports correct output:
Outputs

mgqdrid8xc0us4-assigned-ips
Network IPs assigned to mgqdrid8xc0us4 instance
{
  "novanetwork": [
    "10.0.0.2",
    "172.18.171.111",
    "172.18.171.112"
  ]
}
mgqdrid8xc0us4-floatingIPaddress
Floating IP of mgqdrid8xc0us4
172.18.171.111

murano got following instance settings:
{
                "instance": {
                    "availabilityZone": "nova",
                    "name": "mgqdrid8xc0us4",
                    "securityGroupName": null,
            ---> "assignFloatingIp": true,
                    "ipAddresses": [
                        "10.0.0.2",
                        "172.18.171.111",
                        "172.18.171.112"
                    ],
                    "networks": {
                        "useFlatNetwork": false,
                        "primaryNetwork": null,
                        "useEnvironmentNetwork": true,
                        "customNetworks": []
                    },
                    "keyname": "",
                    "sharedIps": [],
            ---> "floatingIpAddress": null,
                    ...
            }

Changed in murano:
importance: Undecided → High
assignee: nobody → Stan Lagun (slagun)
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/212100

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/212101

tags: added: engine muranopl
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (stable/kilo)

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

commit a5796cbe4532dd7096238f0ed549178a003dfe5d
Author: Stan Lagun <email address hidden>
Date: Wed Aug 12 19:49:48 2015 +0300

    Typo leaded to FIP not being assigned for nova-network

    Because incorrect output name was used for floating IP resource
    in NovaNetwork class Instance tried to access wrong Heat output
    and didn't saw FIP that was actually assigned to the instance

    Change-Id: I8b7bda279bf6ff7514daa7b2168ca5291d613ef4
    Closes-Bug: #1484190

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

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

commit 07c7b3e4cf2943e65e174958bb9f108481331fdd
Author: Stan Lagun <email address hidden>
Date: Wed Aug 12 19:49:48 2015 +0300

    Typo leaded to FIP not being assigned for nova-network

    Because incorrect output name was used for floating IP resource
    in NovaNetwork class Instance tried to access wrong Heat output
    and didn't saw FIP that was actually assigned to the instance

    Change-Id: I8b7bda279bf6ff7514daa7b2168ca5291d613ef4
    Closes-Bug: #1484190

Changed in murano:
status: In Progress → Fix Committed
Changed in murano:
status: Fix Committed → Fix Released
Changed in murano:
milestone: liberty-3 → 1.0.0
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.

Other bug subscribers

Remote bug watches

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