Created attachment 1516985 [details]
vm is registered

Created attachment 1516986 [details]
vm's subscripiton

This issue can be reproduced in sat6.4 and sat6.5, it's hard to reproduce, but it's really exist.

How to reproduce:
1). register virt-who host to sat6.4 or 6.5
2). register vcenter guest to sat6.4 or 6.5
Make sure you never run virt-who for this vcenter and this satellite, the h/g associated info never be sent to this satellite before.
Thus, you can find the Temporary SKU for guest in satellite website, this is expected.

3). Now I will create a virt-who configure file for this vcenter, and make sure the hypervisor_id=uuid, just like:
# cat /etc/virt-who.d/esx.conf
[esx_config]
type=esx
server=xxx.xxx.xxx.xxx
username=administrator
password=xxx
owner=Default_Organization
env=Library
hypervisor_id=uuid

and then I will start virt-who service for this configure file, 
you will find the vcenter's guest is associated with a host in the satellite website. and now there is no any Temporary SKU found for this guest any more, this is expected.

4). this step, I will change the hypervisor_id=hostname in the above configure file:
# cat /etc/virt-who.d/esx.conf
[esx_config]
type=esx
server=xxx.xxx.xxx.xxx
username=administrator
password=xxx
owner=Default_Organization
env=Library
hypervisor_id=hostname

and then I will restart virt-who service for this configure file again,  
you will find the vcenter's guest is associated with the same host in the satellite website. and no any Temporary SKU found for this guest any more, this is expected.

5). now I will unregister the vcenter host in satellite website, that means the association is broken between the vcenter host and guest, the Temporary SKU for the guest should be available.
but the Actual Results: no any Temporary SKU found for this guest


My opinion:
This issue is caused by the duplicated start virt-who service with hypervisor_id=uuid and hypervisor_id=hostname,
Start virt-who service with hypervisor_id=uuid and hypervisor_id=hostname, there are two hyperviosr entry created, but only one hypervisior entry list, another entry is hidden.
Although I unregistered the vcenter host to break the association in satellite website, the hidden association is still exist.

Workaround: Register and Unregister one by one:
start virt-who service with hypervisor_id=uuid, unregistered the hypervisor host in satellite website
start virt-who service with hypervisor_id=hostname, unregistered the hypervisor host in satellite website


if start virt-who service with hypervisor_id=uuid, after that start virt-who service with hypervisor_id=hostname again, you can't unregistered the hypervisor host completely in satellite website，because one of them is hidden.

Hey, 
According to our latest test result, when the a virtual machine is registered to sat6.5, the temporary sku is available and can be attached.

Verified in Satellite 6.7 Beta

Submitted a virt-who report with one guest vm and one hypervisor
Registering a VM to the Satellite properly entitled it with the temporary subscription.
Registering the hypervisor allowed me to attach the vdc sub
This made the guest of <hypervisor> sub available to be attached to the guest.
Attaching the guest sub was then successful on the guest vm.

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/RHSA-2020:1454