Yaniv, please add the qa_ak
I've pushed a patch to configure use of domains in the undercloud heat here
It also requires a fix that has been merged into os-cloud-config
but this fix hasn't mad it into the downstream packaging
os-cloud-config patch merged downstream:
i tested the instack-undercloud patch, and it lgtm so I applied it downstream:
built into: instack-undercloud-2.1.2-6.el7ost
Looking in the current heat-engine.log in the controller node:
2015-07-05 16:24:48.810 8917 WARNING heat.common.config [-] stack_user_domain_
id or stack_user_domain_name not set in heat.conf falling back to using default
And the above parameters are not set in /etc/heat/heat.conf
@Amit: Can you please confirm if that log is from the undercloud heat (e.g the logs on the instack node, not the deployed cloud)?
There is a separate bug for the overcloud heat configuration, bz#1235748, this is only about configuring the undercloud heat service correctly.
Note another way to validate this is to look at the users in the "heat" domain on the undercloud keystone, e.g via python-openstackclient. Without this fix, there will be no "heat" domain or users in it, with it the domain will exist and several users will exist after a successful overcloud deployment.
After testing this one with Steven I can verify the fix for the undercloud installation. Please see https://bugzilla.redhat.com/show_bug.cgi?id=1235748 to monitor the same issue on the overcloud environement
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.