When using the docker container UI the tag information is not being set correctly. 0) Setup docker compute resource + Sync docker images 1) Containers -> Create Container 2) Select lifecycle environment, CV, repository, Tag, Smart Proxy 3) Click next step Note the tag info while getting propagated in the Put request does not get stored in the database making it always choose the latest. This is a side effect of https://github.com/Katello/katello/pull/6775 as part of Issue http://projects.theforeman.org/issues/19468
Created from redmine issue http://projects.theforeman.org/issues/21050
Upstream bug assigned to paji
At this point there are other issues that also happen when the above sequence is selected 1) Error along the lines of "API v1 - Repository images request failed" """ 2017-10-09T00:55:10 cf57435b [app] [D] <Array> [:get, "/v1.16/images/1-docker-rhel7-library-00fc3a70-b91c-47a0-94c8-cbcb42545e04/json", {}, nil] 2017-10-09T00:55:10 cf57435b [app] [D] <Array> [:get, "/v1/repositories/1-docker-rhel7-library-00fc3a70-b91c-47a0-94c8-cbcb42545e04/tags", {}, nil] 2017-10-09T00:55:11 cf57435b [app] [W] API v1 - Repository images request failed ["/home/vagrant/.rvm/gems/ruby-2.2.4/gems/docker-api-1.33.6/lib/docker/connection.rb:46:in `rescue in request'", "/home/vagrant/.rvm/gems/ruby-2.2.4/gems/docker-api-1.33.6/lib/docker/connection.rb:38:in `request'", "/home/vagrant/.rvm/gems/ruby-2.2.4/gems/docker-api-1.33.6/lib/docker/connection.rb:65:in `block (2 levels) in <class:Connection>'", "/home/vagrant/.rvm/gems/ruby-2.2.4/gems/foreman_docker-3.2.1/app/models/service/registry_api.rb:24:in `get'", "/home/vagrant/.rvm/gems/ruby-2.2.4/gems/foreman_docker-3.2.1/app/models/service/registry_api.rb:80:in `get_tags'", "/home/vagrant/.rvm/gems/ruby-2.2.4/gems/foreman_docker-3.2.1/app/models/service ...""" 2) The wrong repository name getting mapped when one is about to create the container.
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/21050 has been resolved.
Verified on Satellite 6.3 snap 24, katello-provided image was correctly provisioned, see attachment.
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-2018:0336