Bug 1190790

Summary: `hammer compute-resource create -h` do not mention Docker
Product: Red Hat Satellite Reporter: Jan Hutař <jhutar>
Component: Container ManagementAssignee: Martin Bacovsky <mbacovsk>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bbuckingham, bkearney, cwelton
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
URL: http://projects.theforeman.org/issues/12116
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-11 20:43:17 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 Jan Hutař 2015-02-09 15:58:28 UTC
Description of problem:
`hammer compute-resource create -h` do not mention Docker. E.g. help text for "--url" says "URL for Libvirt, RHEV, and Openstack". Also in webUI when creating Docker compute resource I see fields "Username", "Password" (I do not know what are these for, but `hammer compute-resource create -h` do not mention Docker in the help text) and "Email" (again, I do not see what is this for, but in hammer I do not see a way how to supply this).


Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150205.0-Satellite-x86_64


How reproducible:
always


Steps to Reproduce:
1. # hammer compute-resource create -h | grep -i Docker


Actual results:
# hammer -u admin -p changeme compute-resource create -h
Usage:
    hammer compute-resource create [OPTIONS]

Options:
 --description DESCRIPTION                    
 --location-ids LOCATION_IDS                 REPLACE locations with given ids
                                             Comma separated list of values.
 --locations LOCATION_NAMES                  Comma separated list of values.
 --name NAME                                  
 --organization-ids ORGANIZATION_IDS         REPLACE organizations with given ids.
                                             Comma separated list of values.
 --organizations ORGANIZATION_NAMES          Comma separated list of values.
 --password PASSWORD                         Password for RHEV, EC2, Vmware, Openstack. Secret key for EC2
 --provider PROVIDER                         Providers include 
 --region REGION                             for EC2 only
 --server SERVER                             for Vmware
 --set-console-password SET_CONSOLE_PASSWORD for Libvirt and Vmware only
                                             One of true/false, yes/no, 1/0.
 --tenant TENANT                             for Openstack only
 --url URL                                   URL for Libvirt, RHEV, and Openstack
 --user USER                                 Username for RHEV, EC2, Vmware, Openstack. Access Key for EC2.
 --uuid UUID                                 for RHEV, Vmware Datacenter
 -h, --help                                  print help


Expected results:
I would expect Docker is mentioned at least in description of "--url" option. If it makes sense, should be there for "--user" and "--password" and maybe "--email" should be added.

Comment 1 RHEL Program Management 2015-02-09 16:13:30 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.

Comment 3 Bryan Kearney 2015-10-08 20:59:47 UTC
Created redmine issue http://projects.theforeman.org/issues/12116 from this bug

Comment 4 Bryan Kearney 2015-10-09 08:03:40 UTC
Upstream bug component is Container Management

Comment 5 Martin Bacovsky 2016-02-10 10:42:20 UTC
Hammer takes the options and descriptions from Apipie docs.

As explained in the upstream issue, this is problem with extensibility of API docs from foreman plugin. This would need support in foreman core as well as in the docker plugin

Comment 6 Bryan Kearney 2017-01-11 20:43:17 UTC
This is an older bug which has been reported upstream. We are not going to track this bug downstream. When the upstream issue is resolved, the next build will contain the fix. Thank you.