Bug 1593453

Summary:	[6.2.15] Satellite creating orphaned consumer ids when receiving virt-who report
Product:	Red Hat Satellite	Reporter:	wclark
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	jcallaha
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.2.14	CC:	jcallaha, wclark
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-02-03 16:27:43 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 wclark 2018-06-20 21:34:19 UTC

Description of problem:

When Satellite 6.2.15 is receiving host-guest mapping from virt-who, some ESXs are starting in an 'orphaned' state (as found by `# foreman-rake katello:clean_backend_objects`).

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

Satellite 6.2.15
virt-who-0.21.7-1.el7_5.noarch

How reproducible:

Happens every time for the affected ESX hosts.

Steps to Reproduce:
1. # foreman-rake katello:clean_backend_objects COMMIT=true    // >0 orphaned consumer IDs found and removed
2. # foreman-rake katello:clean_backend_objects       // 0 orphaned consumer IDs found
3. # systemctl stop virt-who; virt-who -o; systemctl start virt-who
4. # foreman-rake katello:clean_backend_objects       // >0 orphaned consumer IDs found

Actual results:

Some ESX hosts are not having associated 'content hosts' created on Satellite, and cannot receive the subscription

Expected results:

All ESX hosts are having 'content hosts' created successfully and can attach subscriptions

Comment 6 jcallaha 2019-01-10 18:43:43 UTC

Brad, sorry for the delay. I've been unable to reproduce this with the steps outlined in the report. Tested against 6.3.5 and 6.4.1

Comment 7 Bryan Kearney 2020-01-15 21:00:31 UTC

The Satellite Team is attempting to provide an accurate backlog of bugzilla requests which we feel will be resolved in the next few releases. We do not believe this bugzilla will meet that criteria, and have plans to close it out in 1 month. This is not a reflection on the validity of the request, but a reflection of the many priorities for the product. If you have any concerns about this, feel free to contact Red Hat Technical Support or your account team. If we do not hear from you, we will close this bug out. Thank you.

Comment 8 Bryan Kearney 2020-02-03 16:27:43 UTC

Thank you for your interest in Satellite 6. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this, please do not reopen. Instead, feel free to contact Red Hat Technical Support. Thank you.