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.
When registering a host with an activation key that contains custom subscriptions and auto-attach=true, red hat subscriptions are not attached.
Our key contains the following Product Subscriptions: a proprietary product, EPEL, HP, Dell, VMware, Katello Client, Puppet. No Red Hat subs are added as auto-attach should find them automatically. When the host registers, it will add *only* the custom products. Manually running Auto-Attach, the appropriate RH subs are added.
Prior to Katello 2.4, this worked when we added custom subscriptions and all our Red Hat subscriptions to the key (both physical, and virtual datacenter guest subs). Now we are not able to add multiple VDC guest subs to a key.
Our current workaround is to use 2 keys, one for Red Hat subs, and one for custom.
Output in /var/log/candlepin/candlepin.log for the host's UUID during registration:
<pre>
2016-03-14 17:54:20,324 [req=125416ef-d733-4bee-8d53-79c03b5e3770, org=] INFO org.candlepin.resource.ConsumerResource - Consumer e9802fbe-5681-4e04-8627-45e31afbb140 created in org xxxxxxxx
2016-03-14 17:54:22,038 [req=a1d4bee2-7458-420f-9b65-9f54571886e1, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/consumers/e9802fbe-5681-4e04-8627-45e31afbb140
2016-03-14 17:54:23,543 [req=0bdcdf92-c74a-4ec2-a480-023502aed6e4, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/consumers/e9802fbe-5681-4e04-8627-45e31afbb140
2016-03-14 17:54:23,703 [req=1e8ddb2e-5ef1-4768-bcc9-477cf0a45e83, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/consumers/e9802fbe-5681-4e04-8627-45e31afbb140/certificates/serials
2016-03-14 17:54:23,890 [req=2715201d-49c3-43d3-bd5b-e4123242e60c, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/consumers/e9802fbe-5681-4e04-8627-45e31afbb140/certificates?serials=4955668654135756490,621368389686531243,260855579363853393,1109848999340993647,1578481197453257151,718351331378284847,6779464690069033033
2016-03-14 17:54:24,104 [req=1d495dce-699d-40bd-b1a6-36dc2b169a7f, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/consumers/e9802fbe-5681-4e04-8627-45e31afbb140/content_overrides
2016-03-14 17:54:24,230 [req=615bf04a-f5b9-486c-beff-9e9c1e49c291, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/consumers/e9802fbe-5681-4e04-8627-45e31afbb140/compliance
2016-03-14 17:54:24,365 [req=33462f77-14fa-4739-bfdc-5d9915a4d428, org=] INFO org.candlepin.common.filter.LoggingFilter - Request: verb=GET, uri=/candlepin/consumers/e9802fbe-5681-4e04-8627-45e31afbb140
</pre>
An activation key with both Red Hat and custom products will have the Red Hat ones auto-attached and the custom ones always attached. This works correctly in Sat-6.2
Tom McKay could you link to the change that introduced this behaviour? I can't have a single activation key with redhat auto-attach content and custom subscriptions. Tested this as recently as katello 3.3.1
Greetings
Klaas