Description of problem:

Insights client fails with error, providing scant information, when first registering a Cloud Access (BYOL/BYOS) instance on EC2.


Version-Release number of selected component (if applicable):

insights-client --version
Client: 3.0.13-1
Core: 3.0.150-1


How reproducible:

Always


Steps to Reproduce:
1. Stand up a new instance on Ec2 using a RHEL8.0 Cloud Access enabled AMI, in other words bring-your-own-subscription. (e.g. ami-03cda30b7a23bda26).  The new instance can access yum mirrors w/o friction via RHUI

2. Attempt to register client with Red Hat Insight

Actual results:

[root@ip-172-31-42-159 ~]# insights-client --register
Unable to fetch egg url. Defaulting to /release
Could not connect to the Insights API. Run insights-client --test-connection for more information.
[root@ip-172-31-42-159 ~]# insights-client --test-connection
Running Connection Tests...
=== Begin Upload URL Connection Test ===
Testing: https://cert-api.access.redhat.com/r/insights/uploads/
HTTP Status Code: 401
HTTP Status Text: Unauthorized
HTTP Response Text: Insights services authentication failed

Connection failed
=== End Upload URL Connection Test: FAILURE ===

=== Begin API URL Connection Test ===
Testing: https://cert-api.access.redhat.com/r/insights/
HTTP Status Code: 200
HTTP Status Text: OK
HTTP Response Text: lub-dub
Successfully connected to: https://cert-api.access.redhat.com/r/insights/
=== End API URL Connection Test: SUCCESS ===

Connectivity tests completed with some errors
See /var/log/insights-client/insights-client.log for more details.```


Expected results:

Either registration should work, because the instance _is_ entitled via Cloud Access and Insights should be included, or a human readable, meaningful error message should be displayed instead

Additional info:
[root@ip-172-31-1-42 ~]# cat /etc/redhat-release 
Red Hat Enterprise Linux release 8.2 (Ootpa)