Core library can not be imported via client if Glare used as backend
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
python-muranoclient |
Fix Released
|
Critical
|
Alexander Tivelkov |
Bug Description
HOW TO REPRODUCE:
1. Deploy devstack (or use master murano)
2. Explore devstack logs or navigate to murano dashboard to the package manage page
Expected:
Core library is imported correctly
Actual:
There is no core library at all
INFO:
stack@srv66-
stack@srv66-
REQ: curl -g -i -X GET http://
Starting new HTTP connection (1): 172.18.162.71
"GET /v2.0 HTTP/1.1" 200 343
RESP: [200] Date: Mon, 01 Aug 2016 09:37:01 GMT Server: Apache/2.4.7 (Ubuntu) Vary: X-Auth-Token x-openstack-
RESP BODY: {"version": {"status": "stable", "updated": "2014-04-
REQ: curl -g -i -X GET http://
"GET /v2.0 HTTP/1.1" 200 343
RESP: [200] Date: Mon, 01 Aug 2016 09:37:01 GMT Server: Apache/2.4.7 (Ubuntu) Vary: X-Auth-Token x-openstack-
RESP BODY: {"version": {"status": "stable", "updated": "2014-04-
Making authentication request to http://
Starting new HTTP connection (1): 172.18.162.71
"POST /identity/
Importing package io.murano
Error expected a single document in the stream
in "Classes/
but found another document
in "Classes/
Changed in python-muranoclient: | |
milestone: | none → 0.9.1 |
importance: | Undecided → Critical |
status: | New → Confirmed |
Changed in python-muranoclient: | |
assignee: | nobody → Alexander Tivelkov (ativelkov) |
status: | Confirmed → In Progress |
Reviewed: https:/ /review. openstack. org/349452 /git.openstack. org/cgit/ openstack/ python- muranoclient/ commit/ ?id=98adda6a46f d5d2032077758de 1d72cefe4ef55c
Committed: https:/
Submitter: Jenkins
Branch: master
commit 98adda6a46fd5d2 032077758de1d72 cefe4ef55c
Author: Alexander Tivelkov <email address hidden>
Date: Mon Aug 1 14:04:35 2016 +0300
Support for multi-class yamls in client
MuranoClient needs to analyse package classes (names and inheritance
chains) to properly add packages to Glare. This requires it to
properly resolve class names in the appropriate namespaces.
Since Mitaka Murano supports multi-class yamls, i.e. yaml files
containing multiple MuranoPL classes in a single yaml file using it
multi-document format. Optionally this allows to reuse a single
namespace definition for multiple classes defined in the same file.
Client was not aware of this feature, always loading classes as
single-document yamls. It was also always using the current-class
namespace definitions, thus likely to fail if the shared namespace
definition is in use.
This has been addressed.
Closes-bug: #1608440 6c76a2ac517b441 df97311d8b9
Change-Id: Ibd08454f71e026