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.

Description of problem:

When creating repositories and adding them to an existing product using the auto-discover feature, if the product already has a GPG key associated with it, then the new repositories should inherit it.

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


How reproducible:


Steps to Reproduce:

* Create a new Org
* Add environments to Org
* Switch to Org
* Create a new custom provider
* Create a new product
* Import a valid GPG key and associate it with the new product
* Use the Repository Discovery feature to add url http://inecas.fedorapeople.org/fakerepos/ to the new product
  
Actual results:

* Newly created repositories don't have the GPG key associated to them

Expected results:

* Newly created repositories should have the GPG key associated to them

Additional info:

https://github.com/Katello/katello/pull/2975

Tested manually, the gpg-keys are indeed attached automatically for auto discovered repositories from existing product.

Also verified via the gui automation and it passes. 

"Auto-discovered repositories should automatically use GPG keys from product, if associated"

This was verified and delivered with MDP2. Closing it out.

This was delivered and verified with MDP2. Closing the bug.