Red Hat Bugzilla – Bug 1133113
Information about host collection limit is incomplete when looking at content host
Last modified: 2017-02-23 16:02:15 EST
Created attachment 929738 [details] Host Collections capacity Description of problem: Assuming that you create a host collection with unlimited quantity, then associate it with an activation key and use it to register a content host, go to the Content Host page and select it. Then, click the Host Collections tab and watch that the quantity information shows x/ (where x is the quantity used). What is missing here is probably the word 'unlimited' as follows: x/unlimited (see the attached screenshot). Version-Release number of selected component (if applicable): Browser: -------- * Firefox 31.0 Mac OS Build: ------ * Satellite-6.0.4-RHEL-6-20140820.1 Packages: --------- * apr-util-ldap-1.3.9-3.el6_0.1.x86_64 * candlepin-0.9.23-1.el6_5.noarch * candlepin-common-1.0.1-1.el6_5.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.9.23-1.el6_5.noarch * candlepin-tomcat6-0.9.23-1.el6_5.noarch * elasticsearch-0.90.10-6.el6sat.noarch * foreman-1.6.0.41-1.el6sat.noarch * foreman-compute-1.6.0.41-1.el6sat.noarch * foreman-gce-1.6.0.41-1.el6sat.noarch * foreman-libvirt-1.6.0.41-1.el6sat.noarch * foreman-ovirt-1.6.0.41-1.el6sat.noarch * foreman-postgresql-1.6.0.41-1.el6sat.noarch * foreman-proxy-1.6.0.29-1.el6sat.noarch * foreman-selinux-1.6.0.7-1.el6sat.noarch * foreman-vmware-1.6.0.41-1.el6sat.noarch * katello-1.5.0-29.el6sat.noarch * katello-certs-tools-1.5.6-1.el6sat.noarch * katello-default-ca-1.0-1.noarch * katello-installer-0.0.60-1.el6sat.noarch * katello-server-ca-1.0-1.noarch * openldap-2.4.23-32.el6_4.1.x86_64 * pulp-katello-0.3-3.el6sat.noarch * pulp-nodes-common-2.4.0-0.30.beta.el6sat.noarch * pulp-nodes-parent-2.4.0-0.30.beta.el6sat.noarch * pulp-puppet-plugins-2.4.0-0.30.beta.el6sat.noarch * pulp-puppet-tools-2.4.0-0.30.beta.el6sat.noarch * pulp-rpm-plugins-2.4.0-0.30.beta.el6sat.noarch * pulp-selinux-2.4.0-0.30.beta.el6sat.noarch * pulp-server-2.4.0-0.30.beta.el6sat.noarch * python-ldap-2.3.10-1.el6.x86_64 * ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch * ruby193-rubygem-runcible-1.1.0-2.el6sat.noarch * rubygem-hammer_cli-0.1.1-12.el6sat.noarch * rubygem-hammer_cli_foreman-0.1.1-15.el6sat.noarch * rubygem-hammer_cli_foreman_tasks-0.0.3-3.el6sat.noarch * rubygem-hammer_cli_katello-0.0.4-14.el6sat.noarch How reproducible: Steps to Reproduce: 1. Create a new host collection with unlimited quantity 2. Create a new activation key and associate it with the host collection from previous step 3. Use the activation key to register a content host 4. Select your content host from the Content Hosts page and then click the Host Collections tab Actual results: The information about the Capacity used by this host collection does not display the maximum allowed (unlimited) Expected results: The information about the Capacity used by this host collection should display the maximum allowed (unlimited) Additional info:
Created redmine issue http://projects.theforeman.org/issues/8094 from this bug
Proposed fix in PR: https://github.com/Katello/katello/pull/4765
VERIFIED: # rpm -qa | grep foreman foreman-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.2-1.el6_6sat.noarch foreman-compute-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_docker-1.2.0.2-1.el6_6sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el6_6sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.1-1.el6_6sat.noarch foreman-proxy-1.7.2.3-1.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.5-1.el6_6sat.noarch foreman-vmware-1.7.2.8-1.el6_6sat.noarch foreman-libvirt-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_abrt-0.0.5-2.el6_6sat.noarch qe-sat6-rhel66.usersys.redhat.com-foreman-proxy-1.0-2.noarch rubygem-hammer_cli_foreman-0.1.4.6-1.el6_6sat.noarch foreman-selinux-1.7.2.8-1.el6_6sat.noarch foreman-debug-1.7.2.8-1.el6_6sat.noarch foreman-gce-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman-redhat_access-0.0.8-2.el6_6sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.5-1.el6_6sat.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el6_6sat.noarch foreman-postgresql-1.7.2.8-1.el6_6sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.3-1.el6_6sat.noarch foreman-ovirt-1.7.2.8-1.el6_6sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.8-1.el6_6sat.noarch screenshot attached
Created attachment 999509 [details] host collection
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