Hi All,
It's my understanding that I can configure heat to use a keystone domain by referencing the domain by id (stack_user_domain_id) or by name (stack_user_domain_name). Specifying the domain by id works fine. However, when I specify the domain by name (stack_user_domain_name) and create a subsequent stack the stack remains in CREATE_IN_PROGRESS status indefinitely and I see the following in keystone's log:
2014-10-01 10:51:14.531 2926 DEBUG keystone.common.sql.core [-] Conflict project: (IntegrityError) (1452, 'Cannot add or update a child row: a foreign key constraint fails (`keystone`.`project`, CONSTRAINT `fk_project_domain_id` FOREIGN KEY (`domain_id`) REFERENCES `domain` (`id`))') 'INSERT INTO project (id, name, domain_id, description, enabled, extra) VALUES (%s, %s, %s, %s, %s, %s)' ('7ec83ff8ba8942c08fd14f3869110b7c', 'edae0993222646239f9c2cb0b0a31ab3-e89d144d-c35d-49f2-bbb3-5dd7420', 'heat', 'Heat stack user project', 1, '{}') wrapper /usr/local/lib/python2.7/dist-packages/keystone/common/sql/core.py:410
It looks like heat isn't resolving the domain name to id before attempting to create a project under that domain.
I'm using master branch w/ the latest commit being ff1f85c6099dfd285459f7c209f60ff840af2b4a.
Thanks!
--mattt
There's actually two parts to this bug. One being that the domain_id isn't being used explicitly when keystone client API calls are made and the other being that because we set CREATE_IN_PROGRESS explicitly during the creation of a stack object, any failing operation happening before the `stack_task` task where all the events are set leaves the stack output to be in a CREATE_IN_PROGRESS state forever.