Bug 1402945

Summary:	[RFE] Guests should be eligible for the temporary guest pool after migration
Product:	[Community] Candlepin	Reporter:	Barnaby Court <bcourt>
Component:	hypervisor_checkin	Assignee:	candlepin-bugs
Status:	ON_QA ---	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	2.0	CC:	nmoumoul, ojanus, redakkan, yuefliu
Target Milestone:	---	Keywords:	FutureFeature, Triaged
Target Release:	2.9
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	candlepin-2.9.0-1	Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:		Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1685797

Description Barnaby Court 2016-12-08 17:08:05 UTC

When a guest is migrated from one hypervisor to another hypervisor it should be eligible for the temporary guest pool within 24 hours of the migration. 

This will prevent the case where a customer is using VDC subscriptions only and a guest consumers a VDC master sub for itself when it checks in before virt-who has reported on the new host association. 

The flow could be as follows:

Guest is running on Host 1
Guest is consumer a host based entitlement from Host 1
Guest is vmotioned to Host 2
Guest is no longer eligible for entitlement from Host 1 so it is removed
Guest checks in (virt-who has not yet reported new host-guest mapping so Guest has no known hypervisor)
Guest is attached to temporary guest entitlement pool for Host 2
Virt-who checks in and reports on mapping of Guest to Host 2
Guest checks in
Temporary guest entitlement is removed from Guest
Guest follows current logic of auto-attach for host based guest pool.

Comment 1 Barnaby Court 2018-08-03 20:09:49 UTC

The guest pool is now 7 days instead of 24 hour.

Comment 3 Rehana 2020-09-04 14:07:40 UTC

*** Bug 1685797 has been marked as a duplicate of this bug. ***