Murano

No ipAddresses for the Instance in ExistingNeutronNetwork

  1. Series newton
  2. Bug #1649715
Bug #1649715 reported by Stan Lagun
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Fix Released
Critical
Stan Lagun
Newton
Fix Committed
Critical
Alexander Tivelkov
Ocata
Fix Released
Critical
Stan Lagun

Bug Description

When deploying an Instance joined to ExistingNeutronNetwork its ipAddresses property returns an empty list, which is causing most of the applications to fail

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

Changed in murano:
assignee: nobody → Stan Lagun (slagun)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to murano (master)

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

commit 6f787ab5a2c398b9a228bd4c68935bc277c9f093
Author: Stan Lagun <email address hidden>
Date: Tue Dec 13 14:58:11 2016 -0800

    ExistingNeutronNetwork didn't return IPs for the instance

    When deploying an Instance joined to ExistingNeutronNetwork its
    ipAddresses property returned an empty list, which was causing most of
    the applications to fail. This happened because the responsibility of
    managing HOT outputs for the instance IP was moved to the Network
    classes and was implemented for the NeutronNetwork but not the
    ExistingNeutronNetwork.

    This commit moves the logic to the base class for all Neutron networks
    and refactors it so that it could be used for them all

    Change-Id: I552098683e0faeb66f7c622ea8c1d073a82d6338
    Closes-Bug: #1649715

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

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/410711

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/murano 3.1.0

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

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

Reviewed: https://review.openstack.org/410711
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=19b4eb074f84a2fe1142e2882695691d53ce655e
Submitter: Jenkins
Branch: stable/newton

commit 19b4eb074f84a2fe1142e2882695691d53ce655e
Author: Stan Lagun <email address hidden>
Date: Tue Dec 13 14:58:11 2016 -0800

    ExistingNeutronNetwork didn't return IPs for the instance

    When deploying an Instance joined to ExistingNeutronNetwork its
    ipAddresses property returned an empty list, which was causing most of
    the applications to fail. This happened because the responsibility of
    managing HOT outputs for the instance IP was moved to the Network
    classes and was implemented for the NeutronNetwork but not the
    ExistingNeutronNetwork.

    This commit moves the logic to the base class for all Neutron networks
    and refactors it so that it could be used for them all

    Change-Id: I552098683e0faeb66f7c622ea8c1d073a82d6338
    Closes-Bug: #1649715

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.