Seems one of the steps the foreman-installer takes is to kill off the
configuration files that exist in /etc/httpd/config.d and put stuff of its
own in there.
This is a huge problem in my case since I have a local copy of the
repositories for EPEL, Puppet, Foreman and Puppet Dependencies that are
pointed to by a VirtualHost statement. Not cool.
What happens then is all the steps following that event FAIL. I'm working
on a possible work-around, but this is a bit of an annoyance.
The cause is that we manage httpd using the pl-apache module, and the
default behaviour (which we don't change) is to purge configs, so only
managed files are used.
If you have an existing config, it'd be better to integrate that into
Puppet and add our Puppet modules (all published on the Forge and
GitHub), giving you more control over the parameters and then your
configs would be managed instead of being purged.
Some work is needed to expose the Apache module parameters via kafo in
the installer, which'd be the other approach.
–
Dominic Cleal
Red Hat Engineering
I actually cobbled together a workaround for the moment. Since the
"default" virtual host points to /var/www/html, I made "html" a symbolic
link pointing to the repository root. That solved that problem but now I
have others that I'm working through. I'll be posting more later when I
quantify what's going wrong.
On 15/10/14 16:19, Peter Berghold wrote:
Seems one of the steps the foreman-installer takes is to kill off the
configuration files that exist in /etc/httpd/config.d and put stuff of
its own in there.This is a huge problem in my case since I have a local copy of the
repositories for EPEL, Puppet, Foreman and Puppet Dependencies that are
pointed to by a VirtualHost statement. Not cool.What happens then is all the steps following that event FAIL. I’m
working on a possible work-around, but this is a bit of an annoyance.The cause is that we manage httpd using the pl-apache module, and the
default behaviour (which we don’t change) is to purge configs, so only
managed files are used.If you have an existing config, it’d be better to integrate that into
Puppet and add our Puppet modules (all published on the Forge and
GitHub), giving you more control over the parameters and then your
configs would be managed instead of being purged.Some work is needed to expose the Apache module parameters via kafo in
the installer, which’d be the other approach.–
Dominic Cleal
Red Hat Engineering–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
–
Peter L. Berghold Salty.Cowdawg@gmail.com