This bug was initially created as a copy of Bug #1816255 I am copying this bug because: Description of problem: Using an http_proxy with the new ansible-based rhsm (osp13 and osp16) does not implement http_proxies correctly. Consequence: random nodes without direct http/https Internet access will randomly fail to download metadata from various repositories even though a satellite server is configured. This kills the deployment before step1. Here's more information. Using this: ============================================================================ $ cat osp16/site_krynn/rhsm.yaml resource_registry: OS::TripleO::Services::Rhsm: /usr/share/openstack-tripleo-heat-templates/deployment/rhsm/rhsm-baremetal-ansible.yaml parameter_defaults: RhsmVars: rhsm_activation_key: "ak_rhosp16" rhsm_method: "satellite" rhsm_org_id: "krynn" rhsm_satellite_url: "https://sat6.lasthome.solace.krynn" rhsm_baseurl: "https://sat6.lasthome.solace.krynn/pulp/repos" rhsm_server_hostname: "sat6.lasthome.solace.krynn" rhsm_insecure: yes rhsm_rhsm_proxy_hostname: "imladris.lasthome.solace.krynn" rhsm_rhsm_proxy_port: "3128" ============================================================================ In the resulting overcloud, http_proxy is missing from: 1) /etc/yum.conf 2) /etc/rhsm/rhsm.conf (should use subscription-manager config to edit it) 3) /etc/dnf/dnf.conf http_proxy should be configured in all 3 places. With the changes in place, deployment proceeds normally.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2719