This bug has been migrated to another issue tracking site. It has been closed here and may no longer be being monitored.

If you would like to get updates for this issue, or to participate in it, you may do so at Red Hat Issue Tracker .
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.
Bug 2008656 - [RFE] Creating repository using hammer does not have the option of passing in gpg-key-name
Summary: [RFE] Creating repository using hammer does not have the option of passing in...
Keywords:
Status: CLOSED MIGRATED
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Credentials
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: visawant
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-09-28 19:35 UTC by Lai
Modified: 2024-06-06 01:03 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2024-06-06 01:03:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
UI showing it worked (63.66 KB, image/png)
2024-01-23 16:38 UTC, Chris Roberts 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker   SAT-20178 0 None Migrated None 2024-06-06 01:03:56 UTC

Description Lai 2021-09-28 19:35:02 UTC 
Description of problem:
Adding gpg-key to repo creation in hammer only has the option of passing in gpg-key-id and not gpg-key-name.  This is causing failures in automation for creating repos with gpg-key-name.

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

How reproducible:
100%

Steps to Reproduce:
1. Git a 6.10 satellite
2. Run hammer command: hammer repository create --help


Actual results:
                                                                   Possible value(s): 'immediate', 'on_demand'
 --gpg-key-id GPG_KEY_ID                                           Id of the gpg key that will be assigned to the new repository
 --http-proxy[-id]                                                 Name/id of a HTTP Proxy
 --http-proxy-policy HTTP_PROXY_POLICY                             Policies for HTTP Proxy for content sync


Expected results:
There should be an option for gpg-key-name

Additional info:
Also running the command to create gives this error:
# hammer repository create --gpg-key-name something
Could not create the repository:
  Error: Unrecognised option '--gpg-key-name'.
  
  See: 'hammer repository create --help'.
Comment 1 tclemmey 2022-03-22 12:00:13 UTC 
I can confirm and produce the same as mentioned above on 6.10 with '--gpg-key' option:

# hammer repository create --gpg-key="somename"
Could not create the repository:
  Error: Unrecognised option '--gpg-key'.

  See: 'hammer repository create --help'.


While Chapter 14.2 (https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/content_management_guide/managing_custom_file_type_content) does list the '--gpg-key' key name option, the Hammer CLI guide for 6.10 (https://access.redhat.com/documentation/en-us/red_hat_satellite/6.10/html/hammer_cli_guide/reference#hammer-repository-create) seems to have lost this option.
Comment 3 Brad Buckingham 2022-11-03 21:45:29 UTC 
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.
Comment 5 Chris Roberts 2024-01-23 16:37:24 UTC 
This is fixed upstream and should be in 6.15, moving to POST

[vagrant@hammer ~]$ hammer repository create --product-id 65 --organization-id 1 --gpg-key-id 1 --name testgpg --content-type yum
Repository created.
Comment 6 Chris Roberts 2024-01-23 16:38:17 UTC 
Created attachment 2009944 [details]
UI showing it worked
Comment 10 visawant 2024-01-29 15:11:42 UTC 
Failed QA
tested on Satellite 6.15.0 snap 8.0

Additional info:
----------------
[root@satellite-ip ~]# hammer repository create --help | grep "gpg-key*"
 --gpg-key-id NUMBER                            Id of the gpg key that will be assigned to the new repository
[root@satellite-ip ~]# 
[root@satellite-ip ~]# hammer repository create --gpg-key-name something
Could not create the repository:
  Error: Unrecognised option '--gpg-key-name'.
  
  See: 'hammer repository create --help'.
Comment 11 Ian Ballou 2024-05-23 18:27:08 UTC 
From the past comments I think there was a misunderstanding about gpg-key-id and gpg-key-name. We currently support only gpg-key-id, as noted in the BZ description. However, we don't support passing something by name for every association. For example, we also don't support http-proxy-name, only  http-proxy-id. Likewise, we only support product-id and not product-name.

As such, I'm going to turn this BZ into an RFE and remove any version indicators.
Comment 12 Eric Helms 2024-06-06 01:03:58 UTC 
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.
Note You need to log in before you can comment on or make changes to this bug.