Uploaded image for project: 'Satellite'
  1. Satellite
  2. SAT-20178 Creating repository using hammer does not have the option of passing in gpg-key-name
  3. SAT-22874

[QE] Creating repository using hammer does not have the option of passing in gpg-key-name

XMLWordPrintable

    • Icon: Sub-task Sub-task
    • Resolution: Done
    • Icon: Undefined Undefined
    • None
    • None
    • Content Credentials
    • 0
    • False
    • Hide

      None

      Show
      None
    • False
    • 0
    • Phoenix - Content
    • Sprint 127, Sprint 128, Sprint 129, Sprint 130, Sprint 131, Sprint 132

      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:

      1. hammer repository create --gpg-key-name something
        Could not create the repository:
        Error: Unrecognised option '--gpg-key-name'.

      See: 'hammer repository create --help'.

      QE Tracker for https://issues.redhat.com/browse/SAT-20178
      Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2008656

              rhn-support-visawant Vijaykumar Sawant
              satellite-focaccia-bot Focaccia Bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                Resolved: