Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionWaldirio 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:
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.
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.