Docker: Issueshttps://projects.theforeman.org/https://projects.theforeman.org/favicon.ico?16970236342020-06-22T11:16:35ZForeman
Redmine Bug #30181 (New): Docker pull fails to retrieve image from foreman https://projects.theforeman.org/issues/301812020-06-22T11:16:35ZDana Vatavu
<p>Precondition:<br /> katello 3.15<br /> pulp 3<br /> foreman 2.0.1</p>
<p>Steps to reproduce the scenario:<br />1.Create a product<br />2.Add a repo of type docker<br />3.Use a personal docker repo to sync images from it.<br />4.Container Images are being synced with success.<br />5.Create a Content View and promote the images via Lifecycle management.<br />6.On the Content->Container Image Tags the promoted images can be seen with their respective tags(due to promotion lifecycle) can be seen.<br />7.Go on any host associated to the respective LifecycleEnv <br />8. Install docker-engine, add insecure-repo as foreman.xxxx.xxx:5000 <br />9. Perform docker pull with the image name spcified in the table from Step 6<br />Expected result: Container image should be downloaded<br />Actual result: Result of docker pull is unknown: Not found</p> Bug #27515 (Closed): "hammer docker --help" states command not supported while some of its subcom...https://projects.theforeman.org/issues/275152019-08-05T12:26:53ZMartin Bacovskymartin.bacovsky@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1734449">https://bugzilla.redhat.com/show_bug.cgi?id=1734449</a></p>
<p><strong>Description of problem:</strong><br />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:<br />"Unfortunately the server does not support such operation."</p>
<p><strong>Version-Release number of selected component (if applicable):</strong><br />Sat 6.6 snap 13</p>
<p><strong>How reproducible:</strong><br />Deterministic</p>
<p><strong>Steps to Reproduce:</strong><br />1. hammer docker --help</p>
<p><strong>Actual results:</strong><br />Unfortunately the server does not support such operation.</p>
<p><strong>Expected results:</strong><br />As some subcommands are supported, at least help should be viewable without message about command being unsupported</p>
<p><strong>Additional info:</strong><br />It would be nice to have this one fixed in 6.6</p> Bug #27514 (Closed): Remove Docker related commands (Error: undefined method `action' for nil:Nil...https://projects.theforeman.org/issues/275142019-08-05T12:10:09ZMartin Bacovskymartin.bacovsky@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1734448">https://bugzilla.redhat.com/show_bug.cgi?id=1734448</a></p>
<p><strong>Description of problem:</strong><br />For technical reasons, Docker CR commands were not removed while removing Docker CR support. They should be removed in the following versions.<br />Some commands even show undefined method error which is a clear bug.</p>
<p><strong>Version-Release number of selected component (if applicable):</strong><br />Sat 6.6</p>
<p><strong>How reproducible:</strong><br />Deterministic</p>
<p><strong>Steps to Reproduce:</strong><br />1. hammer docker container<br />2. hammer docker container status</p>
<p><strong>Actual results:</strong><br />First command exists (and correctly states "Unfortunately the server does not support such operation.")<br />Second command exists (and incorrectly shows error "Error: undefined method `action' for nil:NilClass")</p>
<p><strong>Expected results:</strong><br />Commands shouldn't exist</p> Bug #27397 (Closed): Some hammer docker commands fail with uninitialized constant HammerCLIKatell...https://projects.theforeman.org/issues/273972019-07-23T22:52:07ZMartin Bacovskymartin.bacovsky@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1730026">https://bugzilla.redhat.com/show_bug.cgi?id=1730026</a></p>
<p>Some hammer commands fail with:</p>
<p>Error: uninitialized constant HammerCLIKatello::LifecycleEnvironmentNameResolvable<br />Did you mean? HammerCLIKatello::LifecycleEnvironmentNameMapping</p>
<p>This definitely happens on `hammer docker manifest list`, but I am yet to discover full scope of the problem.</p>
<p>Version:<br />Satellite 6.6.0 snap 11<br />pulp-server-2.19.1-1.el7sat.noarch<br />satellite-6.6.0-5.beta.el7sat.noarch<br />katello-3.12.0-1.el7sat.noarch<br />foreman-1.22.0.9-1.el7sat.noarch<br />tfm-rubygem-hammer_cli_katello-0.18.0.2-1.el7sat.noarch<br />tfm-rubygem-hammer_cli-0.17.1-2.el7sat.noarch</p> Bug #25874 (Closed): hammer docker manifest list never shows docker tag nameshttps://projects.theforeman.org/issues/258742019-01-17T02:22:48ZPartha Ajipaji@redhat.com
<p>`hammer docker manifest list` has "Tag name" column, but never shows anything in it.</p>
<p>It seems that hammer_cli_foreman_docker/lib/hammer_cli_foreman_docker/docker_manifest.rb file expects tag field with definition of single tag. Meanwhile, API returns "tags" field with array of tags data.</p>
<p>git log on katello/app/models/katello/docker_manifest.rb shows that model used to have `has_one :docker_tag`, but that was changed to `has_many` in late 2016. Marking as Regression since I assume it did work as advertised before that change.</p> Bug #21861 (Closed): hammer --version prints unknown version for the docker pluginhttps://projects.theforeman.org/issues/218612017-12-05T12:12:34ZTomáš Strachotatstracho@redhat.com
<pre>
$ hammer --version
hammer (0.11.0)
* hammer_cli_foreman (0.11.0)
* hammer_cli_foreman_docker (unknown version)
* hammer_cli_katello (0.11.0)
</pre> Feature #20775 (New): Exposed ports support for CLIhttps://projects.theforeman.org/issues/207752017-08-29T01:56:05ZSebastian Gräßl
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1335255">https://bugzilla.redhat.com/show_bug.cgi?id=1335255</a></p>
<p><strong>Description of problem:</strong><br />Similarly with UI Exposed ports support we need same support for CLI:<br />- hammer docker info<br />- hammer docker create<br />- hammer docker update</p>
<p><strong>Steps to Reproduce:</strong><br />1. hammer docker {info,create,update} sub commands lack support for docker exposed ports</p>
<p><strong>Actual results:</strong><br />missing support for exposed ports</p>
<p><strong>Expected results:</strong><br />exposed ports support implemented</p> Bug #16102 (Ready For Testing): hammer docker container status always reports Running: no https://projects.theforeman.org/issues/161022016-08-12T21:56:19ZRanjan Kumarranjankumar188@gmail.comFeature #11672 (Closed): GET /docker/api/v2/registries/:id should return the username fieldhttps://projects.theforeman.org/issues/116722015-09-02T16:37:27ZPartha Ajipaji@redhat.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1259513">https://bugzilla.redhat.com/show_bug.cgi?id=1259513</a> <br /> Description of problem:</p>
<p>When you create a new docker registry, you can optionally provide a username and password. However, our API does not seem to return either of them (see further down for an example of the output generated when using hammer).</p>
<p>Version-Release number of selected component (if applicable):</p>
<ul>
<li>Sat6.1.2-SNAP1</li>
</ul>
<p>How reproducible:</p>
<p>Steps to Reproduce:<br />1. User either hammer cli to fetch information for a docker registry OR access /docker/api/v2/registries/:id directly<br />2.<br />3.</p>
<p>Actual results:</p>
<p>Notice how username and password are not returned</p>
<p>Expected results:</p>
<p>At least the username should be returned by the API call</p>
<p>Additional info:</p>
<p>hammer> docker registry update --id 2 --username='omaciel'<br />Docker registry updated<br />hammer> docker registry info --id 2<br />ID: 2<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />Created at: 2015/09/02 19:28:33<br />Updated at: 2015/09/02 20:24:51</p>
<p>hammer> exit<br />[root@ibm-x3250m4-05 ~]# hammer -u admin -p changeme -d docker registry info --id 2<br />[ INFO 2015-09-02 16:25:06 Init] Initialization of Hammer CLI (0.1.4.12) has started...<br />[DEBUG 2015-09-02 16:25:06 Init] Running at ruby 2.0.0-p598<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli_config.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman_bootdisk.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman_discovery.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/foreman_docker.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/gutterball.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/import.yml has been loaded<br />[ INFO 2015-09-02 16:25:06 Init] Configuration from the file /etc/hammer/cli.modules.d/katello.yml has been loaded<br />[DEBUG 2015-09-02 16:25:06 Connection] Registered: foreman<br />[DEBUG 2015-09-02 16:25:06 API] Global headers: {<br /> :content_type => "application/json",<br /> :accept => "application/json;version=2",<br /> "Accept-Language" => "en" <br />}<br />[ INFO 2015-09-02 16:25:06 Modules] Extension module hammer_cli_foreman (0.1.4.14) loaded<br />[ INFO 2015-09-02 16:25:06 Modules] Extension module hammer_cli_foreman_bootdisk (0.1.2.7) loaded<br />[ INFO 2015-09-02 16:25:06 Modules] Extension module hammer_cli_foreman_discovery (0.0.1.10) loaded<br />[ INFO 2015-09-02 16:25:07 HammerCLI::MainCommand] subcommand organization (HammerCLIForeman::Organization) was removed.<br />[ INFO 2015-09-02 16:25:07 HammerCLI::MainCommand] subcommand organization (HammerCLIKatello::Organization) was created.<br />[ INFO 2015-09-02 16:25:07 Modules] Extension module hammer_cli_gutterball (0.0.1.3) loaded<br />[ INFO 2015-09-02 16:25:07 Modules] Extension module hammer_cli_import (0.10.20) loaded<br />[ INFO 2015-09-02 16:25:07 Modules] Extension module hammer_cli_katello (0.0.7.17) loaded<br />[DEBUG 2015-09-02 16:25:07 Init] Using locale 'en'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli' loaded from '/usr/share/gems/gems/hammer_cli-0.1.4.12/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli@system' loaded from '/usr/share/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli-foreman' loaded from '/usr/share/gems/gems/hammer_cli_foreman-0.1.4.14/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli-foreman@system' loaded from '/usr/share/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer_cli_foreman_docker' loaded from '/usr/share/gems/gems/hammer_cli_foreman_docker-0.0.3.9/locale'<br />[DEBUG 2015-09-02 16:25:07 Init] 'mo' files for locale domain 'hammer-cli-katello' loaded from '/usr/share/gems/gems/hammer_cli_katello-0.0.7.17/locale'<br />[ INFO 2015-09-02 16:25:07 HammerCLI::MainCommand] Called with options: {"option_debug"=>true, "option_username"=>"admin", "option_password"=>"***"}<br />[ INFO 2015-09-02 16:25:07 HammerCLIForemanDocker::DockerCommand] Called with options: {}<br />[ INFO 2015-09-02 16:25:07 HammerCLIForemanDocker::DockerRegistryCommand] Called with options: {}<br />[ INFO 2015-09-02 16:25:07 HammerCLIForemanDocker::DockerRegistryCommand::InfoCommand] Called with options: {"option_id"=>"2"}<br />[ INFO 2015-09-02 16:25:07 API] GET /docker/api/v2/registries/2<br />[DEBUG 2015-09-02 16:25:07 API] Params: {}<br />[DEBUG 2015-09-02 16:25:07 API] Headers: {<br /> :params => {}<br />}<br />[DEBUG 2015-09-02 16:25:07 API] Response: {<br /> "id" => 2,<br /> "name" => "Red Hat Docker Registry",<br /> "url" => "https://registry.access.redhat.com",<br /> "description" => nil,<br /> "created_at" => "2015-09-02T19:28:33Z",<br /> "updated_at" => "2015-09-02T20:24:51Z",<br /> "locations" => [],<br /> "organizations" => []<br />}<br />[DEBUG 2015-09-02 16:25:07 API] Response headers: {<br /> :date => "Wed, 02 Sep 2015 20:25:07 GMT",<br /> :server => "Apache/2.4.6 (Red Hat Enterprise Linux)",<br /> :foreman_version => "1.7.2",<br /> :foreman_api_version => "2",<br /> :x_ua_compatible => "IE=Edge,chrome=1",<br /> :cache_control => "must-revalidate, private, max-age=0",<br /> :x_request_id => "a0fedd63901dfcfed505917ca8ef51bb",<br /> :x_runtime => "0.054340",<br /> :x_rack_cache => "miss",<br /> :x_powered_by => "Phusion Passenger 4.0.18",<br /> :set_cookie => [<br /> [0] "_session_id=BAh7B0kiD3Nlc3Npb25faWQGOgZFRkkiJWNkOTU0ZTRjYjU4ODMyYThjOTc2NmRiMWQwM2M4OWUwBjsAVEkiC2xvY2FsZQY7AEYiB2Vu--67efdbc1c468785e0e4945ace6a6a83ba3907dab; path=/; secure; HttpOnly" <br /> ],<br /> :etag => "\"71f8a3f3f2b750eab907421469b85345\"",<br /> :status => "200 OK",<br /> :transfer_encoding => "chunked",<br /> :content_type => "application/json; charset=utf-8" <br />}<br />ID: 2<br />Name: Red Hat Docker Registry<br />URL: <a class="external" href="https://registry.access.redhat.com">https://registry.access.redhat.com</a><br />Created at: 2015/09/02 19:28:33<br />Updated at: 2015/09/02 20:24:51</p> Bug #10688 (Resolved): docker image list does not show the tag count anymorehttps://projects.theforeman.org/issues/106882015-06-03T08:19:29ZMartin Bacovskymartin.bacovsky@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1221729">https://bugzilla.redhat.com/show_bug.cgi?id=1221729</a> <br /> Description of problem:<br />In the previous output of `hammer docker image list` a column with the tag count was displayed and it not showing anymore.</p>
<p>Version-Release number of selected component (if applicable):<br />Satellite-6.1.0-RHEL-7-20150513.0</p>
<p>How reproducible:<br />Aways</p>
<p>Steps to Reproduce:<br />1. hammer -u admin -p password docker image list</p>
<p>Actual results:<br />The tag count column is not shown</p>
<p>Expected results:<br />The tag count column is shown</p>
<p>Additional info:</p>
<ol>
<li>hammer <del>u admin -p password docker image list<br />------------------------------------</del>|------------------------------------------------------------------|---------<br />ID | IMAGE ID | SIZE<br />-------------------------------------|------------------------------------------------------------------|---------<br />faeee6a8-cacc-498f-b997-2cde24237b5f | e8a999563c473139dc74d02eefb7b13ffea63799bc05b8936b9ad7119b37742f | 5609404<br />ec64c42b-8f3b-487f-bb3e-e373c6adf362 | f6169d24347d30de48e4493836bec15c78a34f08cc7f17d6a45a19d68dc283ac | 0<br />...</li>
</ol> Bug #10386 (Closed): Foreman docker CLI errors are not being reported correctlyhttps://projects.theforeman.org/issues/103862015-05-05T16:32:16ZMartin Bacovskymartin.bacovsky@gmail.com
<p>Cloned from <a class="external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1218409">https://bugzilla.redhat.com/show_bug.cgi?id=1218409</a> <br /> Description of problem:</p>
<p>When I try to create a container twice, I get "Error: 422 Unprocessable Entity" but it doesn't tell me the actual validation error. The API is using the error template in foreman so I am not sure why the error isn't being displayed in the CLI.</p>
<p>$ hammer docker container create --name container1 --compute-resource-id 1 --repository-name redis --tag latest --command bash<br />Sucssefully created container.<br />$ hammer docker container create --name container1 --compute-resource-id 1 --repository-name redis --tag latest --command bash<br />Could not create the container:<br /> Error: 422 Unprocessable Entity</p> Feature #9754 (Closed): Need to be able to create docker registries from the CLIhttps://projects.theforeman.org/issues/97542015-03-13T17:08:46ZDavid Davisdaviddavis@redhat.comBug #9752 (Closed): When creating a container, errors from docker are not properly reported to th...https://projects.theforeman.org/issues/97522015-03-13T16:58:39ZDavid Davisdaviddavis@redhat.com
<p>When I create a container with a dupe name, Docker properly responds with a 409 to let me know that it conflicts with another container. However, we're only showing "500 server error".</p>
<pre>
❯ hammer -u admin -p changeme docker container create --name crafty_turing \
--repository-name centos --tag latest --compute-resource DockerCP --command bash
Docker container created
❯ hammer -u admin -p changeme docker container create --name crafty_turing \
--repository-name centos --tag latest --compute-resource DockerCP --command "ping google.com"
Could not create the container:
Error: 500 Internal Server Error
</pre>
<p>We need to show a user friendly error.</p> Bug #9748 (Ready For Testing): hammer...docker gemspec licence errorshttps://projects.theforeman.org/issues/97482015-03-13T10:42:31ZDominic Clealdominic@cleal.org
<ol>
<li>LICENSE file must be included</li>
<li><del>sample file in config/ should be included for use in packaging</del></li>
<li><del>doc/ should be included</del></li>
<li>license field should be an SPDX ident</li>
</ol> Feature #9682 (New): Add supoprt for i18nhttps://projects.theforeman.org/issues/96822015-03-09T10:13:36ZMartin Bacovskymartin.bacovsky@gmail.com