Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Thanks Stan. It makes sense now. I was able to see the yaml in the database, but I agree that the cached file extension should change to avoid confusion. I appreciate your thorough response. Regards, --Vahid From: Stan Lagun To: "OpenStack Development Mailing List

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Here is the full story: real YAML that is generated is stored in murano database in packages table. Murano Dashboard obtains form definitions in YAML from API. But to improve performance it also caches them locally. And when it does it stores them in Python pickle format [1] rather then original

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Thanks Stan for the pointer. I removed the line that referred to the 'name' property and now my application is added to the environment without any errors. However, what I see in ui.yaml still doesn't look like YAML. I'm attaching samples again. Even for HOT packages the content is not YAML.

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Vahid, I see what is the problem. You are generating UI form that looks like this: Forms: - group0: fields: [] Application: name: $.group0.name ?: type: "io.murano.apps.generated.CsarHelloWorld" Version: 2.2 The problem in in "name: $.group0.name". Previously

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Vahid, The files you attached doesn't look like a YAML at all Sincerely yours, Stan Lagun Principal Software Engineer @ Mirantis On Wed, Nov 25, 2015 at 10:21 PM, Vahid S Hashemian < vahidhashem...@us.ibm.com> wrote: > Kate, Serg, > > Thank you very much for your quick

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Kate, Serg, Thank you very much for your quick responses. I am attaching the requested yaml file. For Hot2 plugin, the only difference with hot_package.py is that I changed the UI translation version to 2.2 and removed predefined_fields in _translate_ui_parameters method. The ui.yaml file is

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Hi Vahid, Forms are rended after app is added to the environment in accordance with the UI definition. UI definition contains yaql expressions and one of your expression is incorrect. Please, share UI yaml so we can find out what's the problem. You can also create a bug that it's not obvious

Re: [openstack-dev] [Murano] 'NoMatchingFunctionException: No function "#operator_." matches supplied arguments' error when adding an application to an environment

Hi Vahid, you can find generated UI definitions for the package here: /tmp/muranodashboard-cache/apps/.../ui/ui.yaml On Wed, Nov 25, 2015 at 12:54 PM, Ekaterina Chernova wrote: > > Hi Vahid, > > Forms are rended after app is added to the environment in accordance with