virtwho.destination error with SubscriptionManagerUnregisteredError

Solution Verified - Updated

Environment

  • RHEL 7
  • RHEL 8
  • RHEL 9

Issue

  • Virtwho.destination error with SubscriptionManagerUnregisteredError.
# systemctl status virt-who.service 
● virt-who.service - Daemon for reporting virtual guest IDs to subscription-manager
   Loaded: loaded (/usr/lib/systemd/system/virt-who.service; disabled; vendor preset: disabled)
   Active: active (running) since Tue 2023-06-13 13:21:06 CST; 8s ago
 Main PID: 20503 (virt-who)
    Tasks: 5 (limit: 203128)
   Memory: 27.6M
   CGroup: /system.slice/virt-who.service
           └─20503 /usr/libexec/platform-python /usr/bin/virt-who

Jun 13 13:21:06 xxx  /usr/bin/virt-who[20503]: 2023-06-13 13:21:06,783 [virtwho.rhsm_log WARNING] MainProcess(20503):MainThread @config.py:init_co>
Jun 13 13:21:06 xxx  /usr/bin/virt-who[20503]: 2023-06-13 13:21:06,784 [virtwho.rhsm_log INFO] MainProcess(20503):MainThread @executor.py:__init__>
Jun 13 13:21:06 xxx  /usr/bin/virt-who[20503]: 2023-06-13 13:21:06,784 [virtwho.rhsm_log INFO] MainProcess(20503):MainThread @main.py:main:176 - U>
Jun 13 13:21:06 xxx  /usr/bin/virt-who[20503]: 2023-06-13 13:21:06,784 [virtwho.rhsm_log INFO] MainProcess(20503):MainThread @main.py:main:178 - U>
Jun 13 13:21:06 xxx  systemd[1]: Started Daemon for reporting virtual guest IDs to subscription-manager.
Jun 13 13:21:06 xxx  /usr/bin/virt-who[20503]: 2023-06-13 13:21:06,797 [virtwho.main INFO] MainProcess(20503):Thread-2 @libvirtd.py:_connect:280 ->
Jun 13 13:21:06 xxx  /usr/bin/virt-who[20503]: 2023-06-13 13:21:06,966 [virtwho.main INFO] MainProcess(20503):Thread-2 @virt.py:_send_data:986 - R>
Jun 13 13:21:07 xxx  /usr/bin/virt-who[20503]: 2023-06-13 13:21:07,799 [virtwho.destination_1932929990258289388 ERROR] MainProcess(20503):Thread-3> virtwho.manager.subscriptionmanager.subscriptionmanager.SubscriptionManagerUnregisteredError: Unabl>              

Resolution

  • The host who running virt-who service should be registered to RHSM first. After attached a VDC subscription to the hypervisor, then unregister the host to clean out previous subscriptions. Finally, re-register the system.

Root Cause

  • The host isn't registered to RHSM when starting virt-who service.
SBR
Components
Category
Tags

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.