Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

After virt-who restart, the Hypervisor update task (Actions::Katello::Host::Hypervisors) in UI shows successfully completed but the information about new ESX is missing or host-guest-mapping has not been updated. 


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

1. Configure virt-who in Satellite
2. Restart virt-who
3. Remove some ESX from the satellite
4. Restart virt-who

Actual results:

The removed ESX is not added back in Satellite UI

Following error noticed in candlepin.log

~~
Unable to queue job: Hypervisor Heartbeat Update; blocked by the following existing jobs: 8af3b8eb794a03aa017a46b4b156554a
~~

Expected results:
all profiles visible on the Web UI.

Additional info:
Looks like regression. 

https://bugzilla.redhat.com/show_bug.cgi?id=1999089
https://bugzilla.redhat.com/show_bug.cgi?id=1927532

Thanks for the details, this issue appears to be duplicate of 2173870. Hence closing the issue.

*** This bug has been marked as a duplicate of bug 2173870 ***

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days