After upgrade to Foreman 1.5.1, wondering about /etc/foreman-proxy/settings.yml.rpmnew

Hi,

I'm new to Foreman. As I'm still at a testing stage, I've upgraded to 1.5.1
(packages on CentOS, so using "yum upgrade ruby* foreman*") following the
upgrade instructions. After upgrade, I've noticed file
/etc/foreman-proxy/settings.yml.rpmnew.

Diff between files /etc/foreman-proxy/settings.yml.rpmnew and
/etc/foreman-proxy/settings.yml.rpm shows some of the settings have been
commented.

I like not loose the new defaults that new config files bring, So I was
thinking about merging the files. I then noticed the comments at the
beginning of file /etc/foreman-proxy/settings.yml:

File managed with puppet

Module: 'foreman_proxy'

As I see the file includes the SSL certificate path generated for my
server, I guess the file was generated by the foreman-installer stuff.

So, should I merge the files manually ? Or is there a way to rebuild this
file ?

Regards,
Laurent.

Hello,

> I'm new to Foreman. As I'm still at a testing stage, I've upgraded to 1.5.1

upgraded from which version? 1.5.0 or 1.4.0?

> I like not loose the new defaults that new config files bring, So I was
> thinking about merging the files. I then noticed the comments at the
> beginning of file /etc/foreman-proxy/settings.yml:
> ### File managed with puppet ###
> ## Module: 'foreman_proxy'
>
> As I see the file includes the SSL certificate path generated for my
> server, I guess the file was generated by the foreman-installer stuff.
>
> So, should I merge the files manually ? Or is there a way to rebuild this
> file ?

Our installer is puppet based, puppet modules are located at
/usr/share/foreman-installer/modules.

Everytime you restart it, it re-deploys your last configuration (it
remembers all your options). You can try to re-run it in a dry-run:

foreman-installer -vn

It should only show the changes that are planned. If you make any
changes to your configuration, this will overwrite them.

I recommend to use our installer for all configuration and try to stay
away from manual file changes. You can ignore rpmnew files as the puppet
modules are authority what should be deployed.

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman

>
> Hello,
>
> > I'm new to Foreman. As I'm still at a testing stage, I've upgraded to
> 1.5.1
>
> upgraded from which version? 1.5.0 or 1.4.0?
>
>
From 1.5.0 to 1.5.1.

> > I like not loose the new defaults that new config files bring, So I was
> > thinking about merging the files. I then noticed the comments at the
> > beginning of file /etc/foreman-proxy/settings.yml:
> > ### File managed with puppet ###
> > ## Module: 'foreman_proxy'
> >
> > As I see the file includes the SSL certificate path generated for my
> > server, I guess the file was generated by the foreman-installer stuff.
> >
> > So, should I merge the files manually ? Or is there a way to rebuild
> this
> > file ?
>
> Our installer is puppet based, puppet modules are located at
> /usr/share/foreman-installer/modules.
>
> Everytime you restart it, it re-deploys your last configuration (it
> remembers all your options). You can try to re-run it in a dry-run:
>
> foreman-installer -vn
>
> It should only show the changes that are planned. If you make any
> changes to your configuration, this will overwrite them.
>
> I recommend to use our installer for all configuration and try to stay
> away from manual file changes. You can ignore rpmnew files as the puppet
> modules are authority what should be deployed.
>
>
>
Thanks for this information. I will ignore rpmnew files.

Regards,
Laurent.

··· On Wednesday, June 18, 2014 8:31:32 PM UTC+2, Lukas Zapletal wrote:

> Thanks for this information. I will ignore rpmnew files.

Well, ignore was not the best advice. You can check them, but there
should not be differences. Read update information, from time to time
we might ask users do to some manual change even for minor upgrades.

··· -- Later,

Lukas “lzap” Zapletal
irc: lzap #theforeman