Initial installation of Satellite 6.7 under hypervisor Virtualbox fails

Solution Verified - Updated -

Issue

  • Why does the installation of satellite 6.7 fail during 'satellite-installer' step, under hypervisor: Virtualbox 6.1.6?
  • Upgrading a Satellite 6.6 system to 6.7 also fails.
# ./satellite-installer --scenario satellite --foreman-initial-organization ORGNAME --foreman-initial-location LOCATIONNAME --foreman-initial-admin-username admin --foreman-initial-admin-password SOMEPASSWORD
Package versions are locked. Continuing with unlock.
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[sat6.local]: Could not evaluate: Proxy sat6.local cannot be retrieved: unknown error (response 500)
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:7:in `proxy'
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:13:in `id'
/usr/share/foreman-installer/modules/foreman/lib/puppet/provider/foreman_smartproxy/rest_v3.rb:17:in `exists?'
/opt/puppetlabs/puppet/lib/ruby/vendor_ruby/puppet/property/ensure.rb:

Environment

  • Host: Microsoft Windows 10 Pro
  • Hypervisor: Oracle Virtualbox 6.1.6
  • Virtual machine: RHEL 7.x
  • Satellite: 6.7

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content