Foreman » Packaging

The error's stating that you don't have :puppet_version set in puppet.yml (usually in /etc/foreman-proxy/settings.d/), see https://theforeman.org/manuals/1.12/index.html#4.3.6Puppet for the configuration - the smart proxy Puppet config files have changed.

If you're using packages, config files should be migrated during the upgrade. I think /var/log/foreman-proxy/migrate_settings.log will contain the process logs.

If you're using a source installation, run rake migrate_settings.

If you're using theforeman/foreman_proxy to configure the smart proxy, upgrade it to the latest version.

Paul Smyth wrote:

I've used packages on Ubuntu, afaik.

Migrate settings log contains this:
/usr/share/foreman-proxy/extra/migrate_settings.rb:16:in `load_past_migrations!': Migration state file /usr/share/foreman-proxy/config/migration_state can't be found (RuntimeError)
from /usr/share/foreman-proxy/extra/migrate_settings.rb:264:in `<main>'

Thanks, this looks like a bug in the Debian package I introduced in 38a2776. Running touch /etc/foreman-proxy/migration_state should fix this for future upgrades.

Adding this has now broken two components instead of one

Disabling all modules in the group ['puppet_proxy_legacy', 'puppet'] due to a failure in one of them: Provider 'puppet_proxy_legacy' settings conflict with the main plugin's settings: [:puppet_conf, :puppet_ssl_ca]

/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:276:in `merge_settings'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:245:in `load_settings'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:81:in `block in load_provider_settings'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:80:in `each'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:80:in `load_provider_settings'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:155:in `block in initialize_plugins'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:155:in `each'
/usr/share/foreman-proxy/lib/proxy/plugin_initializer.rb:155:in `initialize_plugins'
/usr/share/foreman-proxy/lib/launcher.rb:122:in `launch'
/usr/share/foreman-proxy/bin/smart-proxy:6:in `<main>'

This is despite the fact that I've corrected puppet_proxy_legacy.yml to contain the correct entries and confirmed they match puppet.conf

It's likely that you have duplicate entries now between config files, entries that shouldn't be in puppet.yml, though it's hard to tell without seeing all of the configs. There are quite a few steps to the migration, not only that change.

I'd suggest running:

1. touch /etc/foreman-proxy/migration_state
2. ruby /usr/share/foreman-proxy/extra/migrate_settings.rb
3. mkdir ~/foreman-proxy-configs-backup
4. cp -a /etc/foreman-proxy/settings.d/* ~/foreman-proxy-configs-backup/
5. cp /usr/share/foreman-proxy/tmp/result/settings.d/*.yml /etc/foreman-proxy/settings.d/
6. chgrp foreman-proxy /etc/foreman-proxy/settings.d/*.yml
7. service foreman-proxy restart

This should run the proper migrations and activate them.

Applied in changeset d56523cc229f29dc4d2f61f64a3948f40cda3593.