Problem:
During the upgrade from Foreman 2.2.1 to 2.3.1 and Katello from 3.17.1 to 3.18.1 the following can be seen:
Updating : 1:foreman-installer-2.3.1-1.el7.noarch 40/189
warning: /etc/foreman-installer/scenarios.d/foreman.yaml created as /etc/foreman-installer/scenarios.d/foreman.yaml.rpmnew
Updating : 1:foreman-installer-katello-2.3.1-1.el7.noarch 41/189
warning: /etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml created as /etc/foreman-installer/scenarios.d/foreman-proxy-content.yaml.rpmnew
warning: /etc/foreman-installer/scenarios.d/katello.yaml created as /etc/foreman-installer/scenarios.d/katello.yaml.rpmnew
Updating : tfm-rubygem-dynflow-1.4.7-1.fm2_3.el7.noarch 42/189
Updating : rh-ruby25-rubygem-rake-12.3.0-8.el7.noarch 43/189
Installing : tfm-rubygem-server_sent_events-0.1.2-1.el7.noarch 44/189
Updating : tfm-rubygem-rkerberos-0.1.5-19.el7.x86_64 45/189
Installing : tfm-rubygem-excon-0.76.0-1.el7.noarch 46/189
Installing : tfm-rubygem-redfish_client-0.5.2-1.el7.noarch 47/189
Updating : foreman-proxy-2.3.1-1.el7.noarch 48/189
warning: /etc/foreman-proxy/settings.d/bmc.yml created as /etc/foreman-proxy/settings.d/bmc.yml.rpmnew
warning: /etc/foreman-proxy/settings.d/puppet.yml created as /etc/foreman-proxy/settings.d/puppet.yml.rpmnew
The documentation doesn’t state, if we need to take care of that. It states something like “run the installer to take care of possible configuration changes”.
Do we need to adopt the files (like rpmconf -a), can we override them or will the installer take care of that?
Expected outcome:
The upgrade to either:
have no rpmnew files, especially if they haven’t been adopted manually
or
the documentation to let us know what to do
Foreman and Proxy versions:
Foreman 2.3.1
Katello 3.18.1
Foreman and Proxy plugin versions:
Distribution and version:
CentOS 7.9
Other relevant data: