Bug 2169993

Summary:	New Host-guest mapping is not getting populated due to an existing blocked Hypervisor Heartbeat Update job
Product:	Red Hat Satellite	Reporter:	Vedashree Deshpande <vdeshpan>
Component:	Candlepin	Assignee:	Barnaby Court <bcourt>
Status:	CLOSED DUPLICATE	QA Contact:	Vladimír Sedmík <vsedmik>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.11.4	CC:	redakkan
Target Milestone:	Unspecified
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-03-07 14:44:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Vedashree Deshpande 2023-02-15 10:49:06 UTC

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

Comment 3 Rehana 2023-03-07 14:44:14 UTC

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 ***

Comment 4 Red Hat Bugzilla 2023-09-19 04:33:40 UTC

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