Bug 1524528

Summary:	[RFE] Restrict a system to only auto-attach either host-provided subscriptions or temporary guest subscriptions
Product:	Red Hat Satellite	Reporter:	Rajan Gupta <rajgupta>
Component:	Subscriptions - virt-who	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED DUPLICATE	QA Contact:	Eko <hsun>
Severity:	urgent	Docs Contact:
Priority:	urgent
Version:	6.2.12	CC:	bbuckingham, bkearney, dconsoli, hhudgeon, hsun, jalviso, jentrena, khowell, rajgupta, sgao, yuefliu
Target Milestone:	Unspecified	Keywords:	FutureFeature
Target Release:	Unused
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-04-10 14:17:47 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:
Bug Depends On:
Bug Blocks:	1650573

Description Rajan Gupta 2017-12-11 16:18:24 UTC

Description of problem:
Auto-attach on the host running under hypervisor is assigning other subscriptions than VDC.

Auto-attach on the client is not assigning VDC subscriptions from its hypervisor and is taking any other available subscriptions.

Same is happening in case of VMotion of the hosts. A blank activation used to serve the purpose but now that is too failing to work.

Version-Release number of selected component (if applicable):
Red Hat Satellite 6.2.12

Steps to Reproduce:
1. Configure virt-who and map all the hypervisor.
2. Add more subscriptions (physical/virtual) into the satellite.
3. Register a machine using auto attach and it assigns other subscriptions than VDC.

Actual results:
- VMs are assigning themselves a physical or any other subscriptions than VDC.

Expected results:
- VM should be able to inherit the VDC subscriptions when registering a machine.

Additional info:
Most of the issues are seen in 6.2.12.

Comment 2 Kevin Howell 2017-12-14 15:53:57 UTC

Rajan, if you can provide:
 - What are the installed products on the guest?
 - What are the attachments on the hypervisor at the time of the guest auto-attach?
 - What are the available subscriptions in the org?

(some of this is contained in the sosreport)

that would help us troubleshoot/diagnose.

Comment 3 Rajan Gupta 2017-12-14 16:18:22 UTC

Kevin,

Please find the answer to your query.

- What are the installed products on the guest?
A. 69.pem (RHEL)

 - What are the attachments on the hypervisor at the time of the guest auto-attach?
A. "Virtual Data center" (VDC) subscription was attached to the hypervisors

 - What are the available subscriptions in the org?
A. SAP HANA, Red Hat CloudForms, Premium or othe RHEL physical subscriptions.

Regards,
Rajan

Comment 4 Rajan Gupta 2017-12-21 19:11:29 UTC

Hello,

May I request for an update please?

Regards,
Rajan

Comment 5 vritant 2017-12-26 15:12:30 UTC

Rajan,
Apologies for the delayed response. Would appreciate some more information to help troubleshoot this issue.
1. the sos report requested in comment 2 , and
2. Please turn on debug logging on candlepin as per [1], run auto attach from a guest and share the candlepin logs, which should provide us with a lot more details as to what is happening during the autobind.






[1] https://access.redhat.com/documentation/en-us/red_hat_satellite/6.1/html/user_guide/sect-red_hat_satellite-user_guide-maintaining_a_red_hat_satellite_server-enabling_debug_logging

Comment 6 Rajan Gupta 2017-12-26 16:30:27 UTC

Hello Vritant,

Thank you for replying back. I have asked the requested details from Cu and will share as soon as we get those.

Regards,
Rajan

Comment 12 Hayley Hudgeons 2019-04-10 14:17:47 UTC


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