The satellite-installer command fails with error Output of 'facter fqdn' is different from 'hostname -f' in Red Hat Satellite 6

Issue

• Execution of the satellite-installer command fails with the following error:

  /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require': cannot load such file -- hocon (LoadError)
      from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
      from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/core/file_loader.rb:6:in `<top (required)>'
      from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
      from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
      from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter.rb:7:in `<top (required)>'
      from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
      from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
      from /opt/puppetlabs/puppet/lib/ruby/vendor_ruby/facter/framework/cli/cli_launcher.rb:6:in `<top (required)>'
      from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
      from /opt/puppetlabs/puppet/lib/ruby/2.7.0/rubygems/core_ext/kernel_require.rb:83:in `require'
      from /usr/local/bin/facter:5:in `<main>'
  
  Output of 'facter fqdn' is different from 'hostname -f'
  
  Make sure above command gives the same output. If needed, change the hostname permanently via the
  'hostname' or 'hostnamectl set-hostname' command
  and editing the appropriate configuration file.
  (e.g. on Red Hat systems /etc/sysconfig/network,
  on Debian based systems /etc/hostname).
  
  If 'hostname -f' still returns an unexpected result, check /etc/hosts and put
  the hostname entry in the correct order, for example:
  
   1.2.3.4 hostname.example.com hostname
  
  The fully qualified hostname must be the first entry on the line
  Your system does not meet configuration criteria