[katello 2.2] Issue using new Activation Keys

Support
1

Hi,

I upgraded Katello from 2.1 to 2.2 without any issue. Everything is
working great except for one thing: If I create a new activation key, and
register content hosts with it, the hosts are not subscribed to any
product. I've tried creating keys from scratch, copying working ones
(which existed in 2.1), changing the content view for the key, but nothing
seems to work. After the hosts register, I run:

[contenthost]# subscription-manager repos
This system has no repositories available through subscriptions.

I can manually add the subscriptions from the content-hosts administration
page in Katello. After this, all the repos show as expected.

Are there any known issues with Activation Keys, or is there some
workaround I need to employ to get systems registered using Activation Keys?

Thanks.

2

I forgot to mention, auto-attach is set to yes on all the Activation Keys.

··· > >
3

And yet another clarification…If there is a Redhat entitlement, the
Activation Keys work fine. If it's a CentOS Key, it manifests the problem
above.

··· >>
4

This sounds a lot like Bug #10208: Auto-attach subscriptions not working for content hosts with custom products only - Katello - Foreman which is
marked against 2.2.1. If you don't mind adding your scenarios to the bug
information that would help us in debugging.

Thanks,
Eric

··· On Thu, May 14, 2015 at 10:18 AM, GD wrote:

And yet another clarification…If there is a Redhat entitlement, the
Activation Keys work fine. If it’s a CentOS Key, it manifests the problem
above.

–
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an
email to foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.

5

>
> Thanks will do. A (possibly) related issue may be that it seems that I
> can't enable a repo with yum-config-manager when said repo was disabled by
> clicking "override to no" in the activation key. I have puppet modules
> that enable and disable repositories based on hardware requirements. These
> no longer work and executing yum-config-manager --enable (or --enablerepo)
> <repo> has no effect.
>

Thanks.