Foreman-installer overwrite customized ports.conf (/etc/httpd/conf/ports.conf)

Support
1

Hi,

Foreman-installer overwrites my customized ports.conf every time, I'm
wondering whether there are some options for this issue. Let's elaborate it:

On a Foreman server, I have two network interfaces: outside interface NIC1
and internal interface NIC2.

Ports 80/443 and 8140 are listened on both NICs, but by different
applications and for different purposes:

Internal interface NIC2: 80/443/8140 are used by Foreman cluster, and be
taken care of by foreman-installer (apache)
Outside interface NIC1: 80/443/8140 are used by haproxy and linked for
other purposes.

so, when things runs normal, I have the following contents inside
/etc/httpd/conf/ports.conf
Listen NIC1:80
NameVirtualHost *:80
Listen NIC1:443
NameVirtualHost *:443
Listen NIC1:8140
NameVirtualHost *:8140

But after every Foreman-installer runs, say, upgrade, or tuning a few
parameters, the file is reset back to the following:

Listen 80
NameVirtualHost *:80
Listen 443
NameVirtualHost *:443
Listen 8140
NameVirtualHost *:8140

Then surely the 'foreman-run' will fail in the middle, due to httpd/apache
can not startup, because NIC2:80|443|8140 are already occupied (by haproxy).

is there an option like '–foreman-bind-host', similar to
'–foreman-proxy-bind-host' that is available? I'm running Foreman 1.11.3.
Thanks.

2

Internal interface NIC1: 80/443/8140 are used by Foreman cluster, and be
taken care of by foreman-installer (apache)
Outside interface NIC2: 80/443/8140 are used by haproxy and linked for
other purposes.

··· On Tuesday, June 28, 2016 at 6:33:34 PM UTC-7, Thomas Cheng wrote: > > Hi, > > Foreman-installer overwrites my customized ports.conf every time, I'm > wondering whether there are some options for this issue. Let's elaborate it: > > On a Foreman server, I have two network interfaces: outside interface > NIC1 and internal interface NIC2. > > Ports 80/443 and 8140 are listened on both NICs, but by different > applications and for different purposes: > > Internal interface NIC2: 80/443/8140 are used by Foreman cluster, and be > taken care of by foreman-installer (apache) > Outside interface NIC1: 80/443/8140 are used by haproxy and linked for > other purposes. > > so, when things runs normal, I have the following contents inside > /etc/httpd/conf/ports.conf > Listen NIC1:80 > NameVirtualHost *:80 > Listen NIC1:443 > NameVirtualHost *:443 > Listen NIC1:8140 > NameVirtualHost *:8140 > > But after every Foreman-installer runs, say, upgrade, or tuning a few > parameters, the file is reset back to the following: > > Listen 80 > NameVirtualHost *:80 > Listen 443 > NameVirtualHost *:443 > Listen 8140 > NameVirtualHost *:8140 > > Then surely the 'foreman-run' will fail in the middle, due to httpd/apache > can not startup, because NIC2:80|443|8140 are already occupied (by haproxy). > > is there an option like '--foreman-bind-host', similar to > '--foreman-proxy-bind-host' that is available? I'm running Foreman 1.11.3. > Thanks. > > > Sorry, misplaced NIC1/NIC2 at a few places, Here is the correction:
3

Foreman-installer overwrote my customized httpd config files without
warning. If foreman-installer is going to overwrite files and directories
like the httpd conf files it should at least create backups of them.

··· On Tuesday, June 28, 2016 at 8:37:18 PM UTC-5, Thomas Cheng wrote: > > > > On Tuesday, June 28, 2016 at 6:33:34 PM UTC-7, Thomas Cheng wrote: >> >> Hi, >> >> Foreman-installer overwrites my customized ports.conf every time, I'm >> wondering whether there are some options for this issue. Let's elaborate it: >> >> On a Foreman server, I have two network interfaces: outside interface >> NIC1 and internal interface NIC2. >> >> Ports 80/443 and 8140 are listened on both NICs, but by different >> applications and for different purposes: >> >> Internal interface NIC2: 80/443/8140 are used by Foreman cluster, and >> be taken care of by foreman-installer (apache) >> Outside interface NIC1: 80/443/8140 are used by haproxy and linked for >> other purposes. >> >> so, when things runs normal, I have the following contents inside >> /etc/httpd/conf/ports.conf >> Listen NIC1:80 >> NameVirtualHost *:80 >> Listen NIC1:443 >> NameVirtualHost *:443 >> Listen NIC1:8140 >> NameVirtualHost *:8140 >> >> But after every Foreman-installer runs, say, upgrade, or tuning a few >> parameters, the file is reset back to the following: >> >> Listen 80 >> NameVirtualHost *:80 >> Listen 443 >> NameVirtualHost *:443 >> Listen 8140 >> NameVirtualHost *:8140 >> >> Then surely the 'foreman-run' will fail in the middle, due to >> httpd/apache can not startup, because NIC2:80|443|8140 are already occupied >> (by haproxy). >> >> is there an option like '--foreman-bind-host', similar to >> '--foreman-proxy-bind-host' that is available? I'm running Foreman 1.11.3. >> Thanks. >> >> >> Sorry, misplaced NIC1/NIC2 at a few places, Here is the correction: > > Internal interface NIC1: 80/443/8140 are used by Foreman cluster, and be > taken care of by foreman-installer (apache) > Outside interface NIC2: 80/443/8140 are used by haproxy and linked for > other purposes. >
4

Backups should be in Puppet's client bucket. You can find it yourself in
Puppet's vardir (e.g. /var/lib/puppet/clientbucket or
/opt/puppetlabs/puppet/cache/clientbucket) and use scripts such as
https://github.com/rilindo/puppet-clientbucket-restore to restore files
easily.

The installer is only designed for use on a clean OS installation.

··· On 18/07/16 22:42, Andy Ryan wrote: > Foreman-installer overwrote my customized httpd config files without > warning. If foreman-installer is going to overwrite files and > directories like the httpd conf files it should at least create backups > of them.

–
Dominic Cleal
dominic@cleal.org