Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
DescriptionOleksandr Shtaier
2016-03-15 13:53:13 UTC
Description of problem:
In 6.1 we have:
hammer docker --help
Usage:
hammer docker [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND subcommand
[ARG] ... subcommand arguments
Subcommands:
container Manage docker containers
image Manage docker images
registry Manage docker registries
tag Manage docker tags
But in 6.2:
hammer docker --help
Usage:
hammer docker [OPTIONS] SUBCOMMAND [ARG] ...
Parameters:
SUBCOMMAND subcommand
[ARG] ... subcommand arguments
Subcommands:
container Manage docker containers
tag Manage docker tags
However we have corresponding API paths:
Registries:
GET /docker/api/v2/registries List all docker registries
GET /docker/api/v2/registries/:id Show a docker registry
POST /docker/api/v2/registries Create a docker registry
PUT /docker/api/v2/registries/:id Update a docker registry
DELETE /docker/api/v2/registries/:id Delete a docker registry
And they are working fine, so it seems issue is specific for Hammer
Version-Release number of selected component (if applicable):
6.2 SNAP 3.1
How reproducible:
Always
Steps to Reproduce:
1. Try to create docker registry through CLI
Actual results:
Necessary commands are absent in hammer
Expected results:
Necessary operations with docker can be performed successfully
Additional info:
Comment 2Oleksandr Shtaier
2016-03-15 14:36:41 UTC
Oops, it seems API requests to registries are also corrupted
It appears that we need an updated version of hammer_cli_foreman_docker. We currently have tfm-rubygem-hammer_cli_foreman_docker-0.0.3-5.el7sat.noarch; however, we need to pick up the changes that were introduced with 0.0.4. I have added a reference to the redmine issue that introduced those changes.
Description of problem: In 6.1 we have: hammer docker --help Usage: hammer docker [OPTIONS] SUBCOMMAND [ARG] ... Parameters: SUBCOMMAND subcommand [ARG] ... subcommand arguments Subcommands: container Manage docker containers image Manage docker images registry Manage docker registries tag Manage docker tags But in 6.2: hammer docker --help Usage: hammer docker [OPTIONS] SUBCOMMAND [ARG] ... Parameters: SUBCOMMAND subcommand [ARG] ... subcommand arguments Subcommands: container Manage docker containers tag Manage docker tags However we have corresponding API paths: Registries: GET /docker/api/v2/registries List all docker registries GET /docker/api/v2/registries/:id Show a docker registry POST /docker/api/v2/registries Create a docker registry PUT /docker/api/v2/registries/:id Update a docker registry DELETE /docker/api/v2/registries/:id Delete a docker registry And they are working fine, so it seems issue is specific for Hammer Version-Release number of selected component (if applicable): 6.2 SNAP 3.1 How reproducible: Always Steps to Reproduce: 1. Try to create docker registry through CLI Actual results: Necessary commands are absent in hammer Expected results: Necessary operations with docker can be performed successfully Additional info: