On 21/05/20 10:07 am, İzzettin Erdem wrote:

Hi David,

I inspected keystone and heat but there is not any wrong configuration at these services. I think Sahara causes this, because I can create heat stack manually and Murano service can create too. I shared the latest sahara-engine journal below.

http://paste.openstack.org/show/793840/

The resource that's failing is a WaitConditionHandle. This relies on a user created (by Heat) in a separate domain (known, confusingly, as the stack_user).[1] Heat is failing to get a token for this user using the username and password that it assigned when it created the user. This suggests a configuration problem with Heat, or with the setup of the domain that Heat needs in Keystone.[2] You can reproduce outside of Sahara by creating a stack with an OS::Heat::WaitConditionHandle resource. cheers, Zane. [1] https://hardysteven.blogspot.com/2014/04/heat-auth-model-updates-part-2-stac... [2] Prerequisite #5 in one of these install guides: https://docs.openstack.org/heat/latest/install/install.html

Thanks, İzzettin

David Peacock <dpeacock@redhat.com <mailto:dpeacock@redhat.com>>, 15 May 2020 Cum, 20:22 tarihinde şunu yazdı:

Hi izzettin,

That seems pretty fundamental; are you sure you're trying to authenticate this with the correct user?  I'd be checking keystone configuration and logs to see what's going on.

Thanks, David

On Fri, May 15, 2020 at 10:27 AM İzzettin Erdem <root.mch@gmail.com <mailto:root.mch@gmail.com>> wrote:

Hello everyone,

When I launch a cluster on Sahara, it gives a heat stack authorization error. I also use Murano service and it is working with heat. I could not find the solution and I discuss this error with the Sahara-devel team. They are also searching for this. Could you help me, please?

Both the error log of Sahara and Heat are below.

Sahara-engine: http://paste.openstack.org/show/793671/

Heat-engine: http://paste.openstack.org/show/793673/

Thanks. Regards.