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 1085035

Summary: Unable to associate gpg-key to a new product while creating it via repo-discovery
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: RepositoriesAssignee: Justin Sherrill <jsherril>
Status: CLOSED DUPLICATE QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.0.3CC: bbuckingham, rochacbruno
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/5766
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-04-25 15:02:57 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:
Attachments:
Description Flags
gpg-key dropdown doesn't show the key-name none

Description Sachin Ghai 2014-04-07 15:13:28 UTC
Created attachment 883657 [details]
gpg-key dropdown doesn't show the key-name

Description of problem:
I was trying to perform repo-discovery and so far it is working fine. But I found an issue. 

When we create new product while repo-discovery, I got a gpg-key dropdown, but it doesn't show the created key name.

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

* apr-util-ldap-1.3.9-3.el6_0.1.x86_64
* candlepin-0.9.7-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.7-1.el6_5.noarch
* candlepin-tomcat6-0.9.7-1.el6_5.noarch
* elasticsearch-0.90.10-4.el6sat.noarch
* foreman-1.5.0.18-1.el6sat.noarch
* foreman-compute-1.5.0.18-1.el6sat.noarch
* foreman-libvirt-1.5.0.18-1.el6sat.noarch
* foreman-postgresql-1.5.0.18-1.el6sat.noarch
* foreman-proxy-1.5.5-1.el6sat.noarch
* foreman-selinux-1.5.0-0.develop.el6sat.noarch
* katello-1.5.0-19.el6sat.noarch
* katello-apache-1.0-1.noarch
* katello-ca-1.0-1.noarch
* katello-certs-tools-1.5.5-1.el6sat.noarch
* katello-installer-0.0.33-1.el6sat.noarch
* openldap-2.4.23-31.el6.x86_64
* pulp-katello-plugins-0.2-1.el6sat.noarch
* pulp-nodes-common-2.3.1-0.4.beta.el6sat.noarch
* pulp-nodes-parent-2.3.1-0.4.beta.el6sat.noarch
* pulp-puppet-plugins-2.3.1-0.4.beta.el6sat.noarch
* pulp-rpm-plugins-2.3.1-0.4.beta.el6sat.noarch
* pulp-selinux-2.3.1-0.4.beta.el6sat.noarch
* pulp-server-2.3.1-0.4.beta.el6sat.noarch
* python-ldap-2.3.10-1.el6.x86_64
* ruby193-rubygem-ldap_fluff-0.2.2-2.el6sat.noarch
* ruby193-rubygem-net-ldap-0.3.1-3.el6sat.noarch
* ruby193-rubygem-runcible-1.0.8-1.el6sat.noarch
* rubygem-hammer_cli-0.1.0-5.el6sat.noarch
* rubygem-hammer_cli_foreman-0.1.0-6.el6sat.noarch
* rubygem-hammer_cli_foreman_tasks-0.0.2-2.el6sat.noarch
* rubygem-hammer_cli_katello-0.0.3-15.el6sat.noarch


How reproducible:
always

Steps to Reproduce:
1. create an org
2. create new gpgkey as 'g1'
3. go to products page and click on repo-discovery
4. paste this URL http://hhovsepy.fedorapeople.org/fakerepos/ and click on discovery
5. click the discovered repo zoo4
6. create repo
7. now select new_product and enter a new product name
8. click on gpg key drop-down to associate created key in step2
9. drop down doesn't show the key

Actual results:
gpg-key drop down doesn't show the key name to select while performing repo_discovery under new product.

Expected results:
gpg-key drop-down should show the key name to select

Additional info:

Comment 1 RHEL Program Management 2014-04-07 15:27: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.

Comment 3 Brad Buckingham 2014-05-16 20:04:48 UTC
Created redmine issue http://projects.theforeman.org/issues/5766 from this bug

Comment 4 Justin Sherrill 2014-06-05 15:13:58 UTC
This is more of an RFE, moving off 6.0.3

Comment 5 Bryan Kearney 2015-08-25 17:56:32 UTC
Upstream bug component is Content Management

Comment 6 Bryan Kearney 2015-08-25 17:58:10 UTC
Upstream bug component is WebUI

Comment 7 Bruno Rocha 2016-04-25 15:02:57 UTC

*** This bug has been marked as a duplicate of bug 1210180 ***