System registration fails with error HTTPConnectionPool(host='169.xxx.xxx.xxx', port=80): Read timed out. (read timeout=10.0)

Environment

• Red Hat Enterprise Linux 8
• Red Hat Subscription Manager (RHSM)
• Microsoft Hyper-V

Issue

• System registration fails with below error for the VMs running on Microsoft Hyper-V host.

   # subscription-manager register
   Registering to: subscription.rhsm.redhat.com:443/subscription
   Username: <login-id>
   Password: 
   Network error, unable to connect to server. Please see /var/log/rhsm/rhsm.log for more information.
  

   # cat /var/log/rhsm/rhsm.log
   2022-04-20 13:18:43,237 [ERROR] subscription-manager:9123:MainThread @managercli.py:218 - Error during registration: HTTPConnectionPool(host='169.xxx.xxx.xxx', port=80): Read timed out. (read timeout=10.0)
   2022-04-20 13:18:43,237 [ERROR] subscription-manager:9123:MainThread @managercli.py:219 - HTTPConnectionPool(host='169.xxx.xxx.xxx', port=80): Read timed out. (read timeout=10.0)
  

Resolution

• This issue is now resolved with the following Red Hat Bugzilla Advisory. To fully resolve this issue please update the subscription-manager package to subscription-manager-1.28.32-1.el8.x86_64 or later.

• If the update of the subscription-manager package is not immediately possible, then as a workaround, Please follow the below steps to resolve this issue:

  • Create a custom fact file on the system as,

     # vi /etc/rhsm/facts/workaround.facts 
     {
         "dmi.baseboard.manufacturer": "WorkaroundBZ Corporation",
         "dmi.bios.vendor": "WorkaroundBZ Corporation",
         "dmi.chassis.manufacturer": "ssoft Corporation",
         "dmi.memory.manufacturer": "WorkaroundBZ Corporation",
         "dmi.system.manufacturer": "WorkaroundBZ Corporation",
         "lscpu.hypervisor_vendor": "WorkaroundBZ"
     }
    

  • After creating the fact file as above, try again to register the system:

     # subscription-manager clean
     # subscription-manager register
    

For more KB articles/solutions related to Virt-who and Virtual Datacenter (VDC) Subscriptions Issues, please refer to the Consolidated Troubleshooting Article for Virt-who and Virtual Datacenter (VDC) Subscriptions Issues

Root Cause

• This change in behavior was under investigation in Red Hat Bugzilla This content is not included.Bug 2057053 - subscription-manager should not try to gather cloud metadata, when there is not strong sign that the VM is running in public cloud

Diagnostic Steps

• Check the installed version of subscription-manager package:

   # subscription-manager version
   server type: Red Hat Subscription Management
   subscription management server: 3.2.22-1
   subscription management rules: 5.41
   subscription-manager: 1.28.21-3.el8
  

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.