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.
Bug 1317916 - `hammer docker registry` command cannot find its proper routes
Summary: `hammer docker registry` command cannot find its proper routes
Keywords:
Status: CLOSED DUPLICATE of bug 1320338
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Hammer
Version: 6.2.0
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: Unspecified
Assignee: Adam Price
QA Contact: Stephen Benjamin
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-03-15 13:53 UTC by Oleksandr Shtaier
Modified: 2019-04-01 20:26 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-03-31 21:52:02 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 13528 0 None None None 2016-04-22 14:58:26 UTC

Description Oleksandr 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 2 Oleksandr Shtaier 2016-03-15 14:36:41 UTC
Oops, it seems API requests to registries are also corrupted

Comment 3 Brad Buckingham 2016-03-17 19:12:11 UTC
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.

Comment 4 Stephen Benjamin 2016-03-24 19:02:46 UTC
Failed. Registry command doesn't work.

# hammer -u admin -p changeme docker registry list
404 Resource Not Found


/var/log/foreman/production.log

2016-03-24 15:01:15 [app] [I] Started GET "/docker/api/v2/registries?page=1&per_page=1000" for ::1 at 2016-03-24 15:01:15 -0400
2016-03-24 15:01:15 [app] [F] 
 | ActionController::RoutingError (No route matches [GET] "/docker/api/v2/registries"):



Found in: Satellite 6.2 SNAP 5.1

Comment 5 Bryan Kearney 2016-03-24 20:05:08 UTC
Upstream bug assigned to adprice

Comment 6 Adam Price 2016-03-31 16:57:14 UTC
It appears that this bugzilla has changed from its original filing.

Comment 7 Adam Price 2016-03-31 19:46:39 UTC
this fix [1] is needed in Satellite 6 for the routes to generate properly for `/docker` instead of `/foreman_docker`.

[1] http://projects.theforeman.org/issues/14322

Comment 8 Adam Price 2016-03-31 19:53:37 UTC
foreman_docker-2.0.1 is the latest released version of the gem, but it doesn't contain the changes that fix this issue.

Comment 9 Adam Price 2016-03-31 21:52:02 UTC

*** This bug has been marked as a duplicate of bug 1320338 ***


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