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 859646[details]
error while creating gpg-key
Description of problem:
While creating new gpg-key from UI, UI throws error:
Couldn't find organization '{{CurrentOrganization}}'
however org is selected. Please see the attached screenshot
Version-Release number of selected component (if applicable):
satelite6 MDP3 compose1
foreman-proxy-1.5.1-1.el6sat.noarch
foreman-1.5.0.1-1.noarch
rubygem-foreman_api-0.1.11-2.el6sat.noarch
rubygem-hammer_cli_foreman-0.0.18-1.el6sat.noarch
foreman-postgresql-1.5.0.1-1.noarch
foreman-selinux-1.3.0-1.el6sat.noarch
dell-per810-03.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch
dell-per810-03.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch
[root@dell-per810-03 ~]# rpm -qa | grep katello
rubygem-hammer_cli_katello-0.0.2-4.el6sat.noarch
katello-1.5.0-16.el6sat.noarch
katello-certs-tools-1.5.2-1.el6sat.noarch
rubygem-katello_api-0.0.3-3.el6sat.noarch
katello-installer-0.0.20-1.el6sat.noarch
pulp-katello-plugins-0.2-1.el6sat.noarch
katello-candlepin-cert-key-pair-1.0-1.noarch
ruby193-rubygem-katello-1.5.0-13.el6sat.noarch
How reproducible:
always
Steps to Reproduce:
1. Create new gpg-key when org is already selected.
2.
3.
Actual results:
Error on UI: Couldn't find organization '{{CurrentOrganization}}'
Expected results:
gpg key should be created successfully
Additional info:
Comment 1RHEL Program Management
2014-02-05 16:12:17 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Created attachment 859646 [details] error while creating gpg-key Description of problem: While creating new gpg-key from UI, UI throws error: Couldn't find organization '{{CurrentOrganization}}' however org is selected. Please see the attached screenshot Version-Release number of selected component (if applicable): satelite6 MDP3 compose1 foreman-proxy-1.5.1-1.el6sat.noarch foreman-1.5.0.1-1.noarch rubygem-foreman_api-0.1.11-2.el6sat.noarch rubygem-hammer_cli_foreman-0.0.18-1.el6sat.noarch foreman-postgresql-1.5.0.1-1.noarch foreman-selinux-1.3.0-1.el6sat.noarch dell-per810-03.rhts.eng.bos.redhat.com-foreman-proxy-1.0-1.noarch dell-per810-03.rhts.eng.bos.redhat.com-foreman-client-1.0-1.noarch [root@dell-per810-03 ~]# rpm -qa | grep katello rubygem-hammer_cli_katello-0.0.2-4.el6sat.noarch katello-1.5.0-16.el6sat.noarch katello-certs-tools-1.5.2-1.el6sat.noarch rubygem-katello_api-0.0.3-3.el6sat.noarch katello-installer-0.0.20-1.el6sat.noarch pulp-katello-plugins-0.2-1.el6sat.noarch katello-candlepin-cert-key-pair-1.0-1.noarch ruby193-rubygem-katello-1.5.0-13.el6sat.noarch How reproducible: always Steps to Reproduce: 1. Create new gpg-key when org is already selected. 2. 3. Actual results: Error on UI: Couldn't find organization '{{CurrentOrganization}}' Expected results: gpg key should be created successfully Additional info: