Bug #24265
closedRepo discovery: adding GPG key doesn't actually assign it to neither repo nor product
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1595792
Description of problem:
When trying to add a GPG key to a product + repo created by repo discovery, it is not actually added, without any error or traceback. This is a regression.
Version-Release number of selected component (if applicable):
katello-3.7
How reproducible:
Deterministic
Steps to Reproduce:
1. Have an existing GPG key in Content Credentials
2. Content -> Products -> Repo Discovery
3. Fill in type Yum, URL to your repo; click Discover
4. Select some discovered repo, click Create Selected
5. Select new, fill in name, select correct GPG key, click Run Repository Creation
Actual results:
Go to Content Credentials, open the key details, go to Products tab and Repositories tab, they are empty.
Got to Products, select the product, in its detail, check the GPG Key is empty. In its repositories tab, select the repository, check the GPG key is also empty.
Expected results:
The GPG Key assigned to both
Updated by Thomas McKay over 6 years ago
- Subject changed from Repo discovery: adding GPG key doesn't actually assign it to neither repo nor product to Repo discovery: adding GPG key doesn't actually assign it to neither repo nor product
- Team Backlog Tom added
Updated by Jonathon Turel over 6 years ago
- Target version set to Katello 3.7.1
- Triaged changed from No to Yes
Updated by The Foreman Bot over 6 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/7552 added
Updated by Thomas McKay over 6 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset katello|99c554533427536022d65b1279e1b024c24e72d4.