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.