Bug 2040773

Summary: Updating repo with GPG key ID fails
Product: Red Hat Satellite Reporter: Stephen Wadeley <swadeley>
Component: Content CredentialsAssignee: Chris Roberts <chrobert>
Status: CLOSED ERRATA QA Contact: Stephen Wadeley <swadeley>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.11.0CC: chrobert, ehelms, pcreech
Target Milestone: 6.11.0Keywords: Automation, Regression, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: https://projects.theforeman.org/issues/34433
Whiteboard:
Fixed In Version: tfm-rubygem-hammer_cli_katello-1.3.1.6-1 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-07-05 14:32:03 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:

Description Stephen Wadeley 2022-01-14 16:38:48 UTC 
Description of problem:

Adding a GPG key to a repo on the CLI fails


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

How reproducible:
Every time


Steps to Reproduce:
1. Create repo 
2. Create GPG key
3. hammer --debug repository update --id xx --gpg-key-id xx


Actual results:
command returns "Repository updated" but
"hammer repository info --id xx" shows it was not updated

Expected results:

Adding a GPG key to a repo on the CLI works

Additional info:
I did not use Default Org for this test
I will attach foreman debug
Comment 2 Brad Buckingham 2022-01-17 14:16:12 UTC 
Is this a regression from prior releases?
Comment 3 Stephen Wadeley 2022-01-17 19:35:49 UTC 
(In reply to Brad Buckingham from comment #2)
> Is this a regression from prior releases?

Hi Brad

No, this is working OK on 6.10.2

Thank you
Comment 16 errata-xmlrpc 2022-07-05 14:32:03 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: Satellite 6.11 Release), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2022:5498