Bug 1734449

Summary:	"hammer docker --help" states command not supported while some of its subcommands should work
Product:	Red Hat Satellite	Reporter:	Lukáš Hellebrandt <lhellebr>
Component:	Container Management - Content	Assignee:	Martin Bacovsky <mbacovsk>
Status:	CLOSED ERRATA	QA Contact:	Mirek Długosz <mzalewsk>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	6.6.0	CC:	egolov, mbacovsk
Target Milestone:	6.6.0	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	tfm-rubygem-hammer_cli_foreman_docker-0.0.6.4-1	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-22 19:50:27 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 Lukáš Hellebrandt 2019-07-30 14:47:38 UTC

Description of problem:
There are some subcommands of "hammer docker" (e.g. "hammer docker manifest list") that are supposed to work even after removing Docker CR support. However, "hammer docker", including "hammer docker --help", says:
"Unfortunately the server does not support such operation."

Version-Release number of selected component (if applicable):
Sat 6.6 snap 13

How reproducible:
Deterministic

Steps to Reproduce:
1. hammer docker --help

Actual results:
Unfortunately the server does not support such operation.

Expected results:
As some subcommands are supported, at least help should be viewable without message about command being unsupported

Additional info:
It would be nice to have this one fixed in 6.6

Comment 3 Martin Bacovsky 2019-08-05 12:26:56 UTC

Created redmine issue https://projects.theforeman.org/issues/27515 from this bug

Comment 4 Bryan Kearney 2019-08-06 12:04:01 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/27515 has been resolved.

Comment 6 Mirek Długosz 2019-09-02 13:28:01 UTC

`hammer docker --help` includes mention of two subcommands - "manifest" and "tag" ("container" and "registry" are no longer included). Both these subcommands have their own --help messages.

#v+
# hammer docker --help
Usage:
    hammer docker [OPTIONS] SUBCOMMAND [ARG] ...

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

Subcommands:
 manifest                      Manage docker manifests
 tag                           Manage docker tags

Options:
 -h, --help                    Print help
[root@sat-6-6-qa-rhel7 ~]# hammer docker manifest --help
Usage:
    hammer docker manifest [OPTIONS] SUBCOMMAND [ARG] ...

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

Subcommands:
 info                          Show a docker manifest
 list                          List docker_manifests

Options:
 -h, --help                    Print help
[root@sat-6-6-qa-rhel7 ~]# hammer docker tag --help
Usage:
    hammer docker tag [OPTIONS] SUBCOMMAND [ARG] ...

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

Subcommands:
 info                          Show a docker tag
 list                          List docker_tags

Options:
 -h, --help                    Print help
#v-


Tested on:
Satellite 6.6 snap 18
satellite-6.6.0-6.el7sat.noarch
pulp-server-2.19.1.1-1.el7sat.noarch
foreman-1.22.0.21-1.el7sat.noarch
tfm-rubygem-katello-3.12.0.19-1.el7sat.noarch
tfm-rubygem-hammer_cli_katello-0.18.0.4-1.el7sat.noarch
tfm-rubygem-hammer_cli_foreman_docker-0.0.6.4-1.el7sat.noarch
tfm-rubygem-hammer_cli-0.17.1-2.el7sat.noarch
tfm-rubygem-hammer_cli_foreman-0.17.0.7-1.el7sat.noarch

Comment 7 Bryan Kearney 2019-10-22 19:50:27 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, 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-2019:3172