Nested new() are not using 2-phase load

Bug #1608718 reported by Stan Lagun
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Murano
Fix Released
Medium
Stan Lagun

Bug Description

Usually object model load happens in two phases. This is also true for new($model) that does the same at run time. However if the new() happens to be in .init method that is executed as part of object model itself it becomes nested model load. However due to the bug instead of starting another 2-phase session new() joins the same session .init run in (second pass of the outer load). Thus cross object references within the nested model cannot not be resolved.

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/349225
Committed: https://git.openstack.org/cgit/openstack/murano/commit/?id=1d721d7fd605b6f97bd84dce8da2128bb7934467
Submitter: Jenkins
Branch: master

commit 1d721d7fd605b6f97bd84dce8da2128bb7934467
Author: Stan Lagun <email address hidden>
Date: Sat Jul 30 21:54:11 2016 -0700

    Nested new() were not using 2-phase load

    Usually object model load happens in two phases. This is also true for
    new($model) that does the same at run time. However if the new()
    happens to be in .init method that is executed as part of object model
    itself it becomes nested model load. However due to the bug instead of
    starting another 2-phase session, new() used to join the same session
    .init run in (second pass of the outer load). Thus cross object
    references within the nested model were not resolved.

    Closes-Bug: #1608718
    Change-Id: I81396291c3beaee8b0c5b50879313cc236a5aa77

Changed in murano:
status: In Progress → Fix Released
Changed in murano:
importance: Undecided → Medium
milestone: none → newton-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/murano 3.0.0.0b3

This issue was fixed in the openstack/murano 3.0.0.0b3 development milestone.

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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