Bug 1718028

Summary:	Easy way to disable autoheal to current and new hypervisors (standard)
Product:	Red Hat Satellite	Reporter:	Waldirio M Pinheiro <wpinheir>
Component:	Subscription Management	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED WONTFIX	QA Contact:	Cole Higgins <chiggins>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.5.0	CC:	rcavalca, rjerrido, sgraessl
Target Milestone:	Unspecified	Keywords:	Reopened, Triaged
Target Release:	Unused
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-07-09 17:02:24 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 Waldirio M Pinheiro 2019-06-06 17:37:11 UTC

Description of problem:
Sometimes when using entitlement like VDC, SAP VDC, and OpenShift, we get some "unexpected behaviors" like the incorrect entitlement being assigned to the Content Host. One way to resolve this behavior is just disabling autoheal feature (Satellite assigning automatically the entitlement to the hypervisor), however, on the current version, we are able to do this to all current hypervisors, by default, newly discovered hypervisors will land with autoheal enable.

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

How reproducible:
100%

Steps to Reproduce:
1. Install the Satellite
2. Configure virt-who
3. Collect the new info about hypervisor and guests
4. Register the Content Host


Actual results:
Will be assigned the VDC to the hypervisor and Virtual VDC to the Content Host

Expected results:
Be possible via Administer - Settings we define (autoheal = false), then on this case, should be necessary manually attach the entitlement on the hypervisor to only after that the Content Host be able to request the Virtual VDC

Additional info:

Comment 4 Rich Jerrido 2019-06-07 15:15:15 UTC


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

Comment 6 Mike McCune 2021-06-08 21:14:38 UTC

Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 7 Mike McCune 2021-07-09 17:02:24 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 feel free to contact your Red Hat Account Team. Thank you.