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.
Created attachment 713097[details]
System Register using activation key
Description of problem:
As an activation key admin, I'd like to see which systems used it for registration
Version-Release number of selected component (if applicable):
# rpm -qa | grep katello
katello-glue-foreman-1.3.14-1.git.970.ae7918f.el6.noarch
katello-glue-pulp-1.3.14-1.git.970.ae7918f.el6.noarch
katello-common-1.3.14-1.git.970.ae7918f.el6.noarch
katello-selinux-1.3.1-1.el6.noarch
katello-qpid-client-key-pair-1.0-1.noarch
katello-repos-1.3.2-1.el6.noarch
katello-certs-tools-1.1.9-1.el6.noarch
katello-cli-common-1.3.5-1.el6.noarch
katello-glue-elasticsearch-1.3.14-1.git.970.ae7918f.el6.noarch
katello-configure-1.3.6-1.git.838.2dc1245.el6.noarch
katello-all-1.3.14-1.git.970.ae7918f.el6.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
katello-cli-1.3.5-1.el6.noarch
katello-qpid-broker-key-pair-1.0-1.noarch
katello-glue-candlepin-1.3.14-1.git.970.ae7918f.el6.noarch
katello-1.3.14-1.git.970.ae7918f.el6.noarch
How reproducible:
#yum install -y katello-all
#katello-configure --user-pass=PASSWORD
Steps to Reproduce:
1.Login to UI as admin user
2.Navigate to Content -> ActivationKey
3.Click + New Key (create new key)
4.Register and subscribe the system using the activation key
5.Check the ActivationKey tab -> Under System Groups (System)
to view the registered the system
Actual results:
The UI tab displays error
Expected results:
The registered system is visible
Additional info:
Screenshot attached
This bug was closed because of a lack of activity. If you feel this bug should be reconsidered for attention please feel free to re-open the bug with a comment stating why it should be reconsidered.
Created attachment 713097 [details] System Register using activation key Description of problem: As an activation key admin, I'd like to see which systems used it for registration Version-Release number of selected component (if applicable): # rpm -qa | grep katello katello-glue-foreman-1.3.14-1.git.970.ae7918f.el6.noarch katello-glue-pulp-1.3.14-1.git.970.ae7918f.el6.noarch katello-common-1.3.14-1.git.970.ae7918f.el6.noarch katello-selinux-1.3.1-1.el6.noarch katello-qpid-client-key-pair-1.0-1.noarch katello-repos-1.3.2-1.el6.noarch katello-certs-tools-1.1.9-1.el6.noarch katello-cli-common-1.3.5-1.el6.noarch katello-glue-elasticsearch-1.3.14-1.git.970.ae7918f.el6.noarch katello-configure-1.3.6-1.git.838.2dc1245.el6.noarch katello-all-1.3.14-1.git.970.ae7918f.el6.noarch katello-candlepin-cert-key-pair-1.0-1.noarch katello-cli-1.3.5-1.el6.noarch katello-qpid-broker-key-pair-1.0-1.noarch katello-glue-candlepin-1.3.14-1.git.970.ae7918f.el6.noarch katello-1.3.14-1.git.970.ae7918f.el6.noarch How reproducible: #yum install -y katello-all #katello-configure --user-pass=PASSWORD Steps to Reproduce: 1.Login to UI as admin user 2.Navigate to Content -> ActivationKey 3.Click + New Key (create new key) 4.Register and subscribe the system using the activation key 5.Check the ActivationKey tab -> Under System Groups (System) to view the registered the system Actual results: The UI tab displays error Expected results: The registered system is visible Additional info: Screenshot attached