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
2017-06-01 19:20:01 UTC
Description of problem:
When customer use one AK without subscription, the auto-attach works as expected, if customer add one custom subscription, like zabbix or epel for example, the auto-attach doesn't work anymore to the base OS.
Version-Release number of selected component (if applicable):
6.2.9
How reproducible:
100%
Steps to Reproduce:
1. Create one AK without subscription
2. Register the Content Host using this AK, registration worked as expected.
3. Create a new one AK now with subscription related to custom repo *ZABBIX*
4. Register the Content Host using this new AK, registration add only the zabbix repo and bypass the auto attach of base OS.
Actual results:
Subscribe only zabbix repo.
Expected results:
Attach the Zabbix subsc and auto-attach the Base OS subs.
Additional info:
Comment 10Reartes Guillermo
2019-06-18 15:38:36 UTC
This issue does STILL happen with 6.5.0 (!)
Subs -> VDC, several virt-who configs deployed.
Both AKs have auto-attach enabled.
AK without any SUBs -> OK
AK with custom repos subs -> FAILURE
The AK with custom repo subscriptions do have each custom repo set to 'disable' and no other Red Hat subs, since it should use VDC + virt-who.
(In reply to Reartes Guillermo from comment #10)
> This issue does STILL happen with 6.5.0 (!)
>
> Subs -> VDC, several virt-who configs deployed.
>
> Both AKs have auto-attach enabled.
>
> AK without any SUBs -> OK
> AK with custom repos subs -> FAILURE
>
> The AK with custom repo subscriptions do have each custom repo set to
> 'disable' and no other Red Hat subs, since it should use VDC + virt-who.
This is expected behavior. For this use-case it is expected that the customer use 2 activation keys: One to attach virtual subs (which provide access to RHEL) and another to attach the custom sub.
This is documented in
https://access.redhat.com/blogs/1169563/posts/2867891 and in https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/content_management_guide/managing_activation_keys
Comment 13Red Hat Bugzilla
2024-02-04 04:25:04 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days