Bug 2008656
| Summary: | [RFE] Creating repository using hammer does not have the option of passing in gpg-key-name | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Satellite | Reporter: | Lai <ltran> | ||||
| Component: | Content Credentials | Assignee: | satellite6-bugs <satellite6-bugs> | ||||
| Status: | CLOSED MIGRATED | QA Contact: | visawant | ||||
| Severity: | low | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 6.10.0 | CC: | chrobert, iballou, rlavi, tclemmey, visawant | ||||
| Target Milestone: | Unspecified | Keywords: | FutureFeature, MigratedToJIRA | ||||
| Target Release: | Unused | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2024-06-06 01:03:58 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: | |||||||
| Attachments: |
|
||||||
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. 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. 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. Created attachment 2009944 [details]
UI showing it worked
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'. 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. 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. |
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'.