Bug 1979681 - hammer repository --help still shows export subcommand
Summary: hammer repository --help still shows export subcommand
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.10.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: 6.10.0
Assignee: Chris Roberts
QA Contact: Sam Bible
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-07-06 17:34 UTC by Lai
Modified: 2021-11-16 14:12 UTC (History)
3 users (show)

Fixed In Version: tfm-rubygem-hammer_cli_katello-1.1.2.1-1,tfm-rubygem-hammer_cli_katello-1.1.2.2-1
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-11-16 14:12:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32955 0 Normal New hammer repository --help still shows export subcommand 2021-07-07 17:26:47 UTC
Github Katello hammer-cli-katello pull 810 0 None open Fixes #32955 - Remove Pulp2 legacy repo export 2021-07-07 17:43:11 UTC
Github Katello katello pull 9445 0 None open Refs #32955 - Remove old export from repositories controller 2021-07-07 17:43:44 UTC
Red Hat Product Errata RHSA-2021:4702 0 None None None 2021-11-16 14:12:40 UTC

Description Lai 2021-07-06 17:34:27 UTC
Description of problem:
The export command has moved to "hammer content-export" so "hammer repository" shouldn't have the "export" option anymore appearing in help.

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

How reproducible:
100%

Steps to Reproduce:
1. Login to sat via cli
2. Run "hammer repository --help"

Actual results:
# hammer repository --help
Usage:
    hammer repository [OPTIONS] SUBCOMMAND [ARG] ...

Parameters:
 SUBCOMMAND                    Subcommand
 [ARG] ...                     Subcommand arguments

Subcommands:
 create                        Create a custom repository
 delete                        Destroy a custom repository
 export                        Export content from a repository to the 
                                 configured directory
 info                          Show a repository
 list                          List of enabled repositories
 remove-content                Remove content from a repository
 synchronize                   Sync a repository
 update                        Update a repository
 upload-content                Upload content into the repository

Options:
 -h, --help                    Print help


Expected results:
subcommand "export" should not appear anymore.

Additional info:
I'm not sure what else needs to removed from here, but please review them and remove as necessary.

Comment 1 Bryan Kearney 2021-07-14 16:04:07 UTC
Moving this bug to POST for triage into Satellite since the upstream issue https://projects.theforeman.org/issues/32955 has been resolved.

Comment 8 Zach Huntington-Meath 2021-10-07 15:57:24 UTC
No need for cherry-pick automation repicked it up.

Comment 11 Sam Bible 2021-10-14 15:16:15 UTC
Steps to Retest
1. Login to sat via cli
2. Run "hammer repository --help"

Actual results:
# hammer repository --help
Usage:
    hammer repository [OPTIONS] SUBCOMMAND [ARG] ...

Parameters:
 SUBCOMMAND                    Subcommand
 [ARG] ...                     Subcommand arguments

Subcommands:
 create                        Create a custom repository
 delete                        Destroy a custom repository
 info                          Show a repository
 list                          List of enabled repositories
 remove-content                Remove content from a repository
 synchronize                   Sync a repository
 update                        Update a repository
 upload-content                Upload content into the repository

Options:
 -h, --help                    Print help

Verified on 6_10_23 with tfm-rubygem-hammer_cli_katello-1.1.2.2-1.el7sat.noarch

Comment 14 errata-xmlrpc 2021-11-16 14:12:23 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.10 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-2021:4702


Note You need to log in before you can comment on or make changes to this bug.