Httpd fails to start after being updated

Development
#1

Hi,

I am working on issue # 15380 - httpd fails to start after being updated
during upgrade

http://projects.theforeman.org/issues/15380

I was talking to LZAP and he suggested we make the change in the puppet
code. I made the suggestion of having the installer in the pre section do
an rm -rf on the conf.d/ssl.conf file

Thoughts on this?

Thanks,

Chris Roberts

#2

> I was talking to LZAP and he suggested we make the change in the puppet
> code. I made the suggestion of having the installer in the pre section do
> an rm -rf on the conf.d/ssl.conf file

Is clean installation affected as well, or is this upgrade only problem?

I think if we want to prevent RPM from changing ssl.conf, then we should
add it to puppet manifests as a dummy file. Every puppet run should fix
it.

··· -- Later, Lukas #lzap Zapletal
#3

Hi Lzap,

It is only upgrade that looks to be affected. This snip is taken from the
downstream bz

<snip>

To reproduce if you installed satellite after mod_ssl was updated, run:
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.katello && yum reinstall mod_ssl
This is also present in Satellite 6.1

</snip>

  • Chris Roberts
··· On Monday, June 13, 2016 at 11:41:40 AM UTC-4, Lukas Zapletal wrote: > > > I was talking to LZAP and he suggested we make the change in the puppet > > code. I made the suggestion of having the installer in the pre section > do > > an rm -rf on the conf.d/ssl.conf file > > Is clean installation affected as well, or is this upgrade only problem? > > I think if we want to prevent RPM from changing ssl.conf, then we should > add it to puppet manifests as a dummy file. Every puppet run should fix > it. > > -- > Later, > Lukas #lzap Zapletal >
#4

> > > an rm -rf on the conf.d/ssl.conf file

I have a clean Foreman installation on CentOS7 and this file does not
appear to be present:

[root@fseven ~]# rpm -q httpd
httpd-2.4.6-40.el7.centos.1.x86_64

[root@fseven ~]# ls /etc/httpd/conf.d/
05-foreman.conf 05-foreman.d 05-foreman-ssl.conf 05-foreman-ssl.d
15-default.conf 25-puppet.conf passenger.conf

Does it really belong to the httpd package? Isn't it created by a plugin
or some other component?

I am afraid this file was not created by our installer. Can you pastebin
its content?

··· -- Later, Lukas #lzap Zapletal
#5

> > > > an rm -rf on the conf.d/ssl.conf file
>
> I have a clean Foreman installation on CentOS7 and this file does not
> appear to be present:
>
> [root@fseven ~]# rpm -q httpd
> httpd-2.4.6-40.el7.centos.1.x86_64
>
> [root@fseven ~]# ls /etc/httpd/conf.d/
> 05-foreman.conf 05-foreman.d 05-foreman-ssl.conf 05-foreman-ssl.d
> 15-default.conf 25-puppet.conf passenger.conf
>
> Does it really belong to the httpd package? Isn't it created by a plugin
> or some other component?
>
> I am afraid this file was not created by our installer. Can you pastebin
> its content?
>
AFAIU ssl.conf is provided by http package, and out installer removed any
non managed file under apache conf.d directory.

Your suggestion of overriding the file with empty content makes sense to me
as it would ensure it would overridden on upgrade (I assume its marked as
config file).

Ohad

··· On Tue, Jun 14, 2016 at 2:18 PM, Lukas Zapletal wrote:

–
Later,
Lukas #lzap Zapletal

–
You received this message because you are subscribed to the Google Groups
"foreman-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-dev+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

#6

To reproduce if you installed satellite after mod_ssl was updated, run:
mv /etc/httpd/conf.d/ssl.conf /etc/httpd/conf.d/ssl.conf.katello && yum
reinstall mod_ssl

··· On Tuesday, June 14, 2016 at 7:18:52 AM UTC-4, Lukas Zapletal wrote: > > > > > an rm -rf on the conf.d/ssl.conf file > > I have a clean Foreman installation on CentOS7 and this file does not > appear to be present: > > [root@fseven ~]# rpm -q httpd > httpd-2.4.6-40.el7.centos.1.x86_64 > > [root@fseven ~]# ls /etc/httpd/conf.d/ > 05-foreman.conf 05-foreman.d 05-foreman-ssl.conf 05-foreman-ssl.d > 15-default.conf 25-puppet.conf passenger.conf > > Does it really belong to the httpd package? Isn't it created by a plugin > or some other component? > > I am afraid this file was not created by our installer. Can you pastebin > its content? > > > -- > Later, > Lukas #lzap Zapletal >
#7

I agree with Lzap and Ohad that if we just add it to the httpd puppet
module and have it become a dummyfile then it will make sure that all
upgrades go through ok.

··· On Tuesday, June 14, 2016 at 7:26:41 AM UTC-4, ohadlevy wrote: > > > > On Tue, Jun 14, 2016 at 2:18 PM, Lukas Zapletal > wrote: > >> > > > an rm -rf on the conf.d/ssl.conf file >> >> I have a clean Foreman installation on CentOS7 and this file does not >> appear to be present: >> >> [root@fseven ~]# rpm -q httpd >> httpd-2.4.6-40.el7.centos.1.x86_64 >> >> [root@fseven ~]# ls /etc/httpd/conf.d/ >> 05-foreman.conf 05-foreman.d 05-foreman-ssl.conf 05-foreman-ssl.d >> 15-default.conf 25-puppet.conf passenger.conf >> >> Does it really belong to the httpd package? Isn't it created by a plugin >> or some other component? >> >> I am afraid this file was not created by our installer. Can you pastebin >> its content? >> > AFAIU ssl.conf is provided by http package, and out installer removed any > non managed file under apache conf.d directory. > > Your suggestion of overriding the file with empty content makes sense to > me as it would ensure it would overridden on upgrade (I assume its marked > as config file). > > Ohad > >> >> >> -- >> Later, >> Lukas #lzap Zapletal >> >> -- >> You received this message because you are subscribed to the Google Groups >> "foreman-dev" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to foreman-dev...@googlegroups.com . >> For more options, visit https://groups.google.com/d/optout. >> > >