engine should not be including keystone stuff
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
puppet-heat |
Fix Released
|
Medium
|
Matt Fischer |
Bug Description
In the rest of the modules, all of the auth stuff is isolated into a module called keystone/auth.pp, however recent changes to the engine class have added the following:
if $configure_
keystone_role { $trusts_
ensure => present,
}
}
The issue with this is that the nodes I run heat on are not the same as the nodes where I run keystone. This leads to the following error message on the node where I have heat (and not keystone):
Error: /Stage[
I cannot include the engine class in my keystone role either since that won't work.
As far as I can tell in our deployment, this is the only example of a keystone_role outside of an auth file.
Changed in puppet-heat: | |
milestone: | none → 5.0.0 |
Changed in puppet-heat: | |
milestone: | 5.0.0 → 6.0.0 |
Changed in puppet-heat: | |
importance: | Undecided → Medium |
Changed in puppet-heat: | |
status: | Fix Committed → Fix Released |
Changed in puppet-heat: | |
status: | Fix Released → Fix Committed |
Changed in puppet-heat: | |
status: | Fix Committed → Fix Released |
You can set configure_ delegated_ roles to false and declare the keystone_role provider in your own manifest where keystone is running.