Salt Minion installation during deployment fails - Web Proxy issue?

Problem:
Machines deployed/provisioned by Foreman do not install salt-minion and therefore don’t enrol with my salt-master

Foreman and Proxy versions:
[root@deploy01 foreman]# rpm -qa | grep foreman
rubygem-foreman_maintain-1.1.1-3.el8.noarch
rubygem-puppetdb_foreman-5.0.0-4.fm3_3.el8.noarch
foreman-postgresql-3.3.0-1.el8.noarch
rubygem-hammer_cli_foreman-3.3.0-1.el8.noarch
foreman-3.3.0-1.el8.noarch
foreman-installer-katello-3.3.0-1.el8.noarch
rubygem-foreman_monitoring-2.1.0-4.fm3_3.el8.noarch
foreman-dynflow-sidekiq-3.3.0-1.el8.noarch
rubygem-hammer_cli_foreman_tasks-0.0.17-1.fm3_2.el8.noarch
rubygem-foreman_setup-8.0.1-2.fm3_3.el8.noarch
foreman-release-3.3.0-1.el8.noarch
foreman-service-3.3.0-1.el8.noarch
rubygem-foreman-tasks-6.0.2-1.fm3_3.el8.noarch
rubygem-foreman_salt-15.1.0-3.fm3_3.el8.noarch
rubygem-foreman_host_reports-1.0.2-3.fm3_3.el8.noarch
foreman-cli-3.3.0-1.el8.noarch
rubygem-foreman_remote_execution-7.1.0-1.fm3_3.el8.noarch
rubygem-hammer_cli_foreman_remote_execution-0.2.2-1.fm3_0.el8.noarch
foreman-proxy-3.3.0-1.el8.noarch
foreman-installer-3.3.0-1.el8.noarch
rubygem-foreman_puppet-4.0.1-1.fm3_3.el8.noarch
foreman-debug-3.3.0-1.el8.noarch
[root@deploy01 foreman]# rpm -qa | grep salt
salt-3004.2-1.el8.noarch
salt-minion-3004.2-1.el8.noarch
salt-syndic-3004.2-1.el8.noarch
rubygem-smart_proxy_salt-5.0.0-3.fm3_3.el8.noarch
salt-master-3004.2-1.el8.noarch
salt-api-3004.2-1.el8.noarch
rubygem-foreman_salt-15.1.0-3.fm3_3.el8.noarch
salt-ssh-3004.2-1.el8.noarch

Deployment works fine, I have the salt tab when I create a host and my states have been imported successfully from the salt-master (which is the foreman server).

I can see during deployment yum attempts to install something, I’m assuming it’s the salt-minion, but it fails as we’re in a production environment isolated from the internet. We do have a squid proxy which these machines can utilise, but not sure where to set that parameter for this salt-minion installation.

The proxy is set in the General and Content sections of the Foreman → Administer → Settings page.

cc @bastian-src :salt:

I’ve been messing about with my provisioning ks and worked this out!