Hi folks!
I’ve tried to debug this problem and found strange behavior of auth in [1].
So, at least, if in murano.conf we have parameter use_trusts=True,
keystone_client.tenant_name returns None [2].
I’ve tried to use v3 auth instead of v2 and, accordingly, replaced tenant_name
for auth by trust_id
Just to keep track, Victor started a bug on that:
https://bugs.launchpad.net/murano/+bug/1474938/ Haven’t looked close into the
problem, yet, though. Will try to do so some time soon.
--
Kirill Zaitsev
Murano team
Software Engineer
Mirantis, Inc
On 15 Jul 2015 at 16:44:24, Filip Blaha (filip.b
Hi Filip,
Did you get this resolved? If not, could you point me to the gate
failure? I'm on #congress for higher-bandwidth communication.
Tim
On Wed, Jul 15, 2015 at 6:39 AM Filip Blaha wrote:
> Hi all
>
> our congress integration tests were broken by the change [1] (trusts
> enabled by d
Hi all
our congress integration tests were broken by the change [1] (trusts
enabled by default). However I suspect problem could be with
initialization congress client [2] or in python-congressclient. Any
ideas about that? Thanks
[1] https://review.openstack.org/#/c/194615/
[2]
https://gi
