Bug 1011012

Summary: Subscribing with activation key stopped working after adding new custom repo
Product: Red Hat Satellite Reporter: Tom McKay <tomckay>
Component: Content ManagementAssignee: Katello Bug Bin <katello-bugs>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: NightlyCC: rytis.sileika
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 1011005 Environment:
Last Closed: 2013-09-23 13:46:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Tom McKay 2013-09-23 13:25:50 UTC 
+++ This bug was initially created as a clone of Bug #1011005 +++

Description of problem:

Subscription with activation keys worked fine until I created a new custom repo and attached it to the activation key.

Now I'm getting: "Multi-entitlement not supported for pool with id '...'" when I try using the key.

I've tried creating a new AK and adding repos to it:
- Added RHEL repo - works ok
- Added another custom repo - failure

May be worth pointing out that I have 15 or so custom repos and those were added over time with no problems. I did not do any updates on Katello server.

# rpm -qa|grep katello
katello-common-1.3.26-1.el6.noarch
katello-glue-candlepin-1.3.26-1.el6.noarch
katello-cli-1.3.12-1.el6.noarch
katello-repos-1.3.4-1.el6.noarch
katello-configure-1.3.11-1.el6.noarch
katello-glue-pulp-1.3.26-1.el6.noarch
katello-glue-elasticsearch-1.3.26-1.el6.noarch
katello-1.3.26-1.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-cli-common-1.3.12-1.el6.noarch
katello-certs-tools-1.3.1-1.el6.noarch
katello-selinux-1.3.2-1.el6.noarch
katello-all-1.3.26-1.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
Comment 1 Tom McKay 2013-09-23 13:46:05 UTC 

*** This bug has been marked as a duplicate of bug 1011005 ***