Bug #5766

Unable to associate gpg-key to a new product while creating it via repo-discovery

Added by Brad Buckingham about 6 years ago. Updated 9 months ago.

Target version:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:


Cloned from
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-
  • foreman-compute-
  • foreman-libvirt-
  • foreman-postgresql-
  • 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:

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 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:


#1 Updated by Brad Buckingham about 6 years ago

  • Triaged set to Yes

#2 Updated by Eric Helms over 4 years ago

  • Legacy Backlogs Release (now unused) set to 114

#3 Updated by Bryan Kearney over 4 years ago

  • Category changed from Web UI to Repositories

#4 Updated by Justin Sherrill over 3 years ago

  • Assignee deleted (Justin Sherrill)

#5 Updated by John Mitsch 9 months ago

  • Target version deleted (Katello Backlog)
  • Status changed from New to Rejected

Thanks for reporting this issue. This issue was created over 4 years ago and hasn't seen an update in 1 year. We are closing this in an effort to keep a realistic backlog. Please open up a new issue that includes a link to this issue if you feel this still needs to be addressed. We can then triage the new issue and reassess.

Also available in: Atom PDF