Type name resolution fails
Bug #1618563 reported by
Stan Lagun
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Murano |
Fix Released
|
High
|
Stan Lagun | ||
Bug Description
When one class creates instance of another without specifying class FQN but using short name instead and both classes are in different namespaces the class cannot be created because its name is looked up in the wrong namespace. This bug was introduced after new contract framework merge
| Changed in murano: | |
| assignee: | nobody → Stan Lagun (slagun) |
| status: | New → In Progress |
| Changed in murano: | |
| importance: | Undecided → High |
| milestone: | none → newton-3 |
| tags: | added: engine |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix merged to murano (master) | #1 |
| Changed in murano: | |
| status: | In Progress → Fix Released |
Revision history for this message
| OpenStack Infra (hudson-openstack) wrote Fix included in openstack/murano 3.0.0.0b3 | #2 |
To post a comment you must log in.
Reviewed: https:/
Committed: https:/
Submitter: Jenkins
Branch: master
commit 8757c6d177bbfe7
Author: Stan Lagun <email address hidden>
Date: Tue Aug 30 09:35:49 2016 -0700
Type name resolution was fixed
After the new contract framework and new property validation
workflow were introduced type name resolution broke. As
a result if the creating class is in different than the created
property validation will fail. This commit fixes it.
Change-Id: I2fdf7bb5e5d6af
Closes-Bug: #1618563