If rhsm.conf is missing proxy_scheme, and a proxy is configured, leapp assumes the scheme is https. If the proxy is http, the update fails.

This example is a satellite customer so there is a backup of rhsm.conf to compare. 

~~~
# grep proxy_scheme etc/rhsm/rhsm.conf*
  etc/rhsm/rhsm.conf.rpmnew:proxy_scheme = http
# grep proxy_scheme etc/rhsm/rhsm.conf* -c
  etc/rhsm/rhsm.conf:0
  etc/rhsm/rhsm.conf.rpmnew:1


# grep ^proxy etc/rhsm/rhsm.conf
  proxy_hostname = 10.108.132.161
  proxy_port = 3128
  proxy_user =
  proxy_password =

# grep proxy etc/yum.repos.d/redhat.repo | sort -u
  proxy = http://10.108.132.161:3128
~~~


leapp is defaulting to https

~~~
# sqlite3 leapp.db 'select message_data from messages_data where context = "7d5f75e8-3c0e-4f40-a5ee-f28eaa23d50d"' | jq . | grep 10.108.132.161 -C1 | tail -n3
  "configured_proxies": [
    "https://10.108.132.161:3128"
  ],
~~~


Expectation:
If proxy_scheme is missing, and a proxy is present, then we should report that and request the user correct the missing variable in /etc/rhsm/rhsm.conf