Red Hat Bugzilla – Bug 1289667
aodh removes keystone configuration when manifest is applied (resulting in keystone 404's)
Last modified: 2016-04-18 02:52:36 EDT
After a complete mitaka packstack installation, there are no errors from the installation dialog.
However, when I want to use the packstack installation, I sourced the keystonerc file and noticed there would be keystone 404's - therefore I could not do anything.
In Mitaka, both keystone and aodh are set to run as wsgi under Apache.
When the aodh manifest runs, it removes the apache configuration that was previously set for keystone.
This is likely due to be because of the default puppet-apache behavior to purge configuration it doesn't know about. Since keystone and aodh both run in separate manifest files, they each have their own catalog and therefore don't know about each other - resulting in configuration purge.
Created attachment 1103649 [details]
Example OSC keystone 404
Created attachment 1103650 [details]
Puppet excerpt of keystone being set up properly
Created attachment 1103651 [details]
Puppet excerpt of aodh removing keystone configuration
Ooops, this was found when testing the unmerged review https://review.openstack.org/#/c/251988/.
it seems that the aodh puppet module is not calling the apache class with the "purge_configs => false" directive, this might be an openstack-puppet-modules bug
(In reply to David Moreau Simard from comment #4)
> Ooops, this was found when testing the unmerged review
ok, I'll close is dup of bug 1285314 to keep discussion in one place.
*** This bug has been marked as a duplicate of bug 1285314 ***