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.

Bug 1510639

Summary: host registration fails during provisioning if using a limited host collection
Product: Red Hat Satellite Reporter: Og Maciel <omaciel>
Component: Subscription ManagementAssignee: Brad Buckingham <bbuckingham>
Status: CLOSED ERRATA QA Contact: Kedar Bidarkar <kbidarka>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.3.0CC: bbuckingham, ehelms, kbidarka, sghai, zhunting
Target Milestone: UnspecifiedKeywords: PrioBumpQA, Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: rubygem-katello-3.4.5.43-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-02-21 16:54:17 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 Og Maciel 2017-11-07 21:43:58 UTC
Description of problem:


The problem boils down to this: if you're provisioning a host (libvirt in my case) using a host group/activationkey/host collection where the host collection is set to a limit, the registration process fails with the error:

  Host collection 'RHEL 7' exceeds maximum usage limit of '5'

If you change the host collection to unlimited, then registration proceeds without a glitch

 
Version-Release number of selected component (if applicable):

* satellite-6.3.0-21.0.beta.el7sat.noarch

How reproducible:


Steps to Reproduce:
1. Sync content and add it to a content view
2. Publish/promote content view
3. Create activation key, associate it to the content view AND set a limit of 5 hosts
4. Create a host collection is set a limit of 5 hosts
5. Associate the host collection to the activation key
6. Provision a new host using the host group created earlier


Actual results:

The host will provision but it will not be registered


Expected results:


Additional info:

See logs further down

Comment 3 Og Maciel 2017-11-07 22:08:29 UTC
Even if I set the host collection to unlimited host limit and manually attempt to register an existing host, I still get the same error:

# subscription-manager register --org="dc8079af-8e04-4d63-897c-2ecbf89aad78" --activationkey="ak-rhel-70"
Host collection 'RHEL 7' exceeds maximum usage limit of '5'

For new registrations, this works fine.

Comment 4 Brad Buckingham 2017-12-13 15:09:34 UTC
Created redmine issue http://projects.theforeman.org/issues/21961 from this bug

Comment 5 Satellite Program 2017-12-14 17:14:46 UTC
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21961 has been resolved.

Comment 8 Kedar Bidarkar 2018-01-30 06:36:28 UTC
I have a setup ready with snap31+, will pick this up and verify this.

Comment 11 Kedar Bidarkar 2018-01-30 08:52:37 UTC
VERIFIED with sat63.0-snap32.0

Comment 12 Satellite Program 2018-02-21 16:54:17 UTC
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-2018:0336