Project

General

Profile

Bug #21961

host registration fails during provisioning if using a limited host collection

Added by Brad Buckingham almost 4 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Category:
Subscriptions
Target version:
Difficulty:
Triaged:
Bugzilla link:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1510639

Description of problem:

The problem boils down to this: if you're registering a host using an activation key where the host collection is set to a limit, the registration process fails with the error:

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

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

reproduced w/ katello devel environment

How reproducible:

Steps to Reproduce:
1. create a host collection with a limit
2. create an activation key and associate the host collection
3. register a host with the activation key

Actual results:

  1. subscription-manager register --org="Default_Organization" --activationkey="rhel7_filtered" --force
    Host collection 'hc1' exceeds maximum usage limit of '50'

Expected results:

registration succeeds without error

Associated revisions

Revision 6562474d (diff)
Added by Brad Buckingham almost 4 years ago

fixes #21961 - fix host collection check during register

This commit is to put back the logic removed with commit
91599327 that removed the check of the host collection hosts
against the host collection max_hosts.

History

#1 Updated by Brad Buckingham almost 4 years ago

  • Target version set to 240
  • Subject changed from host registration fails during provisioning if using a limited host collection to host registration fails during provisioning if using a limited host collection

#2 Updated by The Foreman Bot almost 4 years ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/Katello/katello/pull/7112 added

#3 Updated by Andrew Kofink almost 4 years ago

  • Legacy Backlogs Release (now unused) set to 329

#4 Updated by Brad Buckingham almost 4 years ago

  • % Done changed from 0 to 100
  • Status changed from Ready For Testing to Closed

Also available in: Atom PDF