Description of problem: I was confused about following and I was explained some background which revealed there is some change in default activation key behavior from Satellite 6.0 to 6.1: > > > I have activation key with 2 repos included: > > > > > > MyActivationKey > > > Product Content > > > both mine products have "Enabled?: Yes (Default)" > > > Subscriptions > > > List/Remove > > > both mine products have "Attached: 1 out of Unlimited" > > > > > > When I register client with: > > > > > > # subscription-manager register --org="Default_Organization" > > > --activationkey="MyActivationKey" > > > > > > I'm not attached to any repos now. I have to do this: > > > > > > # subscription-manager list --available > > > # subscription-manager attach --pool <pool_I_want> > > > > > > Any idea on what should I do better to simplify the process? > > From: "Elyézer Rezende" <erezende> > > > > There is an auto-attach feature for Activation Keys and Jake can provide > > more information on it better than me. Will check with him if he can help > > you. > From: Tom McKay <thomasmckay> > > There is a change: If the activation key has auto-attach on, then the subs > are used as a list to auto-subscribe from; they are not all forced to attach > to the content host. Turn auto-attach off for 6.0 behavior where all subs > are applied. > > We need to change this. Version-Release number of selected component (if applicable): Satellite-6.1.0-RHEL-6-20150210.0-Satellite-x86_64 How reproducible: always Steps to Reproduce: 1. Create 2 custom products and activation key as described above 2. By default, when the key gets created "Auto-Attach" is set to "Yes" (note: what happens to the keys created in 6.0 when we upgrade to 6.1?) 3. Attempt to register system using that activation key Actual results: `yum repolist` says that after registration I do not have any repositories Expected results: `yum repolist` should say that I have repos from these two products added to the activation key Additional info: Maybe this is just documentation bug which should go to release notes, but this change introduces change change in default behaviour of activation keys from 6.0 to 6.1.
Since this issue was entered in Red Hat Bugzilla, the release flag has been set to ? to ensure that it is properly evaluated for this release.
Jan, this not currently considered a bug, but a feature of auto-attach itself. If auto-attach is enabled, then custom products won't be added to the content host. Auto-attach much be turned off for them to make it. I think this is more of an RFE.
Custom products are now attached regardless of auto-attach flag setting, p-r https://github.com/Katello/katello/pull/5043
Verified in Satellite 6.1.0 snap 5. Version tested: RHEL 66 RHEL 7
This bug is slated to be released with Satellite 6.1.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2015:1592