Open Stack

Hi Nikolay & Filip,

indeed, root cause of the issue is that Murano & Mistral use different
version of yaql library. Murano installs yaql 0.2.4 and overrides
1.0.0b2 already installed and expected by Mistral.

We decided that we are not going to switch to the yaql 1.0.0 in Kilo
since we already finished Kilo development and working on bug-fixes
and releasing RC. This gate may be fixed if only Mistral will revert
1.0.0 support in Kilo :'(

Nikolay, what do you think about migrating to YAQL 1.0.0 in the next
release? I know that it was me who proposed Mistral team to adopt yaql
1.0.0, and I am sorry, I didn't realize all consequences of moving
Mistral to yaql 1.0.0 and Murano team living with yaql 0.2.4.

We need to work on packaging and supporting yaql in Ubuntu/CentOS in
order to add this library to the global-requirements and to avoid this
kind of issues in the future.

On Mon, Apr 13, 2015 at 3:58 PM, Nikolay Makhotkin
<nmakhotkin at mirantis.com> wrote:
>>
>> We are facing an issue with Mistral devstack installation in our gate job testing murano-congress-mistral integration (policy enforcement) [1] . Mistral devstack scripts are failing with following import error [2]
>
>
> Hi, Filip!
>
> Recently Mistral has moved to new YAQL, and it seems this dependency is missed (yaql 1.0, currently yaql 1.0.0b2)
>
> I think the root of problem is that Murano and Mistral have different yaql versions installed.
>
> --
> Best Regards,
> Nikolay
>
> __________________________________________________________________________
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: OpenStack-dev-request at lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>



-- 
Serg Melikyan, Senior Software Engineer at Mirantis, Inc.
http://mirantis.com | smelikyan at mirantis.com