Could not get default values after upgrade to 2.1.0

Support
1

Problem:
After upgrade foreman from 2.0.1 to 2.1.0, as usual i run the “foreman-installer” command, but this time i got the following error:
Could not get default values

The error seems related to TLS version but not sure how to resolve it. There is no issue in resolving the hostname. I also able to skip running "foreman-installer’ command and start the service.

Foreman and Proxy versions:
2.1.0

Distribution and version:
CentOS 7.8

Other relevant data:

  ' | RUBYLIB=/opt/theforeman/tfm/root/usr/share/gems/gems/kafo-4.1.0/lib/kafo/../..//modules: /bin/puppet apply --config=/tmp/kafo_installation20200709-13956-1
wdcov6/puppet.conf
[ERROR 2020-07-09T21:45:02 main] /opt/rh/rh-ruby25/root/usr/share/gems/gems/openssl-2.1.2/lib/openssl/ssl.rb:20:in `<class:SSLContext>': uninitialized constant Open
SSL::SSL::TLS1_VERSION (NameError)
    from /opt/rh/rh-ruby25/root/usr/share/gems/gems/openssl-2.1.2/lib/openssl/ssl.rb:18:in `<module:SSL>'
    from /opt/rh/rh-ruby25/root/usr/share/gems/gems/openssl-2.1.2/lib/openssl/ssl.rb:17:in `<module:OpenSSL>'
    from /opt/rh/rh-ruby25/root/usr/share/gems/gems/openssl-2.1.2/lib/openssl/ssl.rb:16:in `<top (required)>'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/rh/rh-ruby25/root/usr/share/gems/gems/openssl-2.1.2/lib/openssl.rb:21:in `<top (required)>'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/securerandom.rb:4:in `<top (required)>'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util.rb:12:in `<top (required)>'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet.rb:14:in `<top (required)>'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/util/command_line.rb:12:in `<top (required)>'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
    from /opt/puppetlabs/puppet/bin/puppet:4:in `<main>'

[ERROR 2020-07-09T21:45:02 main] Could not get default values, cannot continue
2

This looks like a similar root cause as reported in:

This suggests that Puppet is executed in the SCL context. I haven’t been able to figure out why this happens.

In your case, /bin/puppet gives a hint. Do you by any chance have a wrapper there to call Puppet? That probably breaks our logic to de-SCL the environment.

3

Hi,

The /bin/puppet is symlink to /opt/puppetlabs/bin/puppet. After rename /bin/puppet, im able to run the foreman-installer without any issues.

4

@ehelms opened Bug #30365: Puppet bin scripts that exist outside AIO environment as symlinks to AIO puppet bin files break installation in SCL - Kafo - Foreman to track this