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

[Anastasia Kuznetsova]

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,
                    ...
            }

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[OpenStack Infra (hudson-openstack)]

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

[Doug Hellmann (doug-hellmann)]

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

[OpenStack Infra (hudson-openstack)]

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