Description of problem: Nagios puppet modules disable SSL after the Horizon module enables it. Version-Release number of selected component (if applicable): openstack-packstack-2013.2.1-0.22.dev956.el6ost.noarch How reproducible: 100% Steps to Reproduce: 1. packstack --os-horizon-ssl=y --allinone 2. (wait) Actual results: After completion, SSL for Apache is disabled - thus, Horizon SSL does not work. Expected results: Unknown. The Nagios module reset the Apache configuration to largely default, clearing out the Apache SSL configuration performed by the Horizon module. Additional info: packstack --os-horizon-ssl=y --nagios-install=n --allinone ...works fine...
Modifying the nagios template so it uses the SSL configuration given by horizon.
patch submitted to gerrit code review: https://review.openstack.org/#/c/68557/ The nagios template uses the apache class, this class overwrites the current configuration thus deleting the horizon configurations. By checking if horizon is installed this patch avoids the use of the apache puppeet class in the nagios template.
The nagios template uses the apache class, this class overwrites the current configuration thus deleting the horizon configurations. By checking if horizon is installed this patch avoids the use of the apache puppeet class in the nagios template.
Installed it with both nagios and horizon ssl enabled, and it resulted in a working https installation. Verified.
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. http://rhn.redhat.com/errata/RHSA-2014-0233.html