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.
DescriptionElyézer Rezende
2015-03-26 13:27:03 UTC
Description of problem:
A custom image was created by committing an image from a running container but it is not possible to create a new container using it.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150324.0
How reproducible:
Aways
Steps to Reproduce:
1. Create a container using for example centos and running a command like top
2. Power it on and click on commit to create a new image based on the running container
3. Go to New Container wizard, select the same compute resource where the previous image was created (the same for the previous running container)
4. Select the Docker Hub tab and search for the given image name and tag. The search will be able to find the image on Compute Resource
5. Proceed until the last step and try to complete it
Actual results:
The container is not created and no error message is shown
Expected results:
The container is created without any issue
Additional info:
Even though the UI does not show an error the logs shows the following:
==> /var/log/messages <==
Mar 26 09:12:13 ibm-x3250m4-06 docker: time="2015-03-26T09:12:13-04:00" level="info" msg="POST /v1.15/images/create?fromImage=omaciel%2Ftopcentos%3Alatest"
Mar 26 09:12:13 ibm-x3250m4-06 docker: time="2015-03-26T09:12:13-04:00" level="info" msg="+job pull(omaciel/topcentos, latest)"
Mar 26 09:12:13 ibm-x3250m4-06 docker: time="2015-03-26T09:12:13-04:00" level="info" msg="+job resolve_repository(omaciel/topcentos)"
Mar 26 09:12:13 ibm-x3250m4-06 docker: time="2015-03-26T09:12:13-04:00" level="info" msg="-job resolve_repository(omaciel/topcentos) = OK (0)"
Mar 26 09:12:13 ibm-x3250m4-06 docker: endpoint.newEndpoint: starting with address=registry.access.redhat.com, secure=false
Mar 26 09:12:13 ibm-x3250m4-06 docker: endpoint.newEndpoint: address after prefixing: http://registry.access.redhat.com
Mar 26 09:12:13 ibm-x3250m4-06 docker: endpoint.newEndpoint: trimmedAddress=http://registry.access.redhat.com, version=
Mar 26 09:12:13 ibm-x3250m4-06 docker: endpoint.newEndpoint: terminating
Mar 26 09:12:14 ibm-x3250m4-06 docker: Error: image omaciel/topcentos:latest not found
Mar 26 09:12:14 ibm-x3250m4-06 docker: time="2015-03-26T09:12:14-04:00" level="info" msg="+job resolve_repository(docker.io/omaciel/topcentos)"
Mar 26 09:12:14 ibm-x3250m4-06 docker: time="2015-03-26T09:12:14-04:00" level="info" msg="-job resolve_repository(docker.io/omaciel/topcentos) = OK (0)"
Mar 26 09:12:14 ibm-x3250m4-06 docker: endpoint.newEndpoint: starting with address=https://index.docker.io/v1/, secure=true
Mar 26 09:12:14 ibm-x3250m4-06 docker: endpoint.newEndpoint: address after prefixing: https://index.docker.io/v1/
Mar 26 09:12:14 ibm-x3250m4-06 docker: endpoint.newEndpoint: trimmedAddress=https://index.docker.io, version=v1
Mar 26 09:12:14 ibm-x3250m4-06 docker: endpoint.newEndpoint: terminating
Mar 26 09:12:14 ibm-x3250m4-06 docker: time="2015-03-26T09:12:14-04:00" level="info" msg="+job trust_update_base()"
==> /var/log/foreman/production.log <==
2015-03-26 09:12:13 [I] Processing by Containers::StepsController#update as HTML
2015-03-26 09:12:13 [I] Parameters: {"utf8"=>"✓", "authenticity_token"=>"Es/Q1odtOZ9poJaxx4idxiVnY5oAU4s4oj5osv900dQ=", "docker_container_wizard_states_environment"=>{"tty"=>"1", "attach_stdin"=>"1", "attach_stdout"=>"1", "attach_stderr"=>"1"}, "wizard_state_id"=>"2", "id"=>"environment"}
2015-03-26 09:12:13 [I] String does not start with the prefix 'encrypted-', so ForemanDocker::Docker docker was not decrypted
==> /var/log/messages <==
Mar 26 09:12:15 ibm-x3250m4-06 docker: time="2015-03-26T09:12:15-04:00" level="info" msg="-job trust_update_base() = OK (0)"
Mar 26 09:12:15 ibm-x3250m4-06 docker: endpoint.newEndpoint: starting with address=https://registry-1.docker.io/v2/, secure=true
Mar 26 09:12:15 ibm-x3250m4-06 docker: endpoint.newEndpoint: address after prefixing: https://registry-1.docker.io/v2/
Mar 26 09:12:15 ibm-x3250m4-06 docker: endpoint.newEndpoint: trimmedAddress=https://registry-1.docker.io, version=v2
Mar 26 09:12:15 ibm-x3250m4-06 docker: endpoint.newEndpoint: terminating
Mar 26 09:12:15 ibm-x3250m4-06 docker: Error: image omaciel/topcentos:latest not found
Mar 26 09:12:15 ibm-x3250m4-06 docker: time="2015-03-26T09:12:15-04:00" level="info" msg="-job pull(docker.io/omaciel/topcentos, latest) = ERR (1)"
==> /var/log/foreman/production.log <==
2015-03-26 09:12:15 [I] Failed to save:
2015-03-26 09:12:15 [I] Rendered /opt/rh/ruby193/root/usr/share/gems/gems/foreman_docker-1.2.0.7/app/views/foreman_docker/common_parameters/_environment_variable.html.erb (0.7ms)
2015-03-26 09:12:15 [I] Rendered /opt/rh/ruby193/root/usr/share/gems/gems/foreman_docker-1.2.0.7/app/views/containers/steps/_form_buttons.html.erb (0.6ms)
2015-03-26 09:12:15 [I] Rendered /opt/rh/ruby193/root/usr/share/gems/gems/foreman_docker-1.2.0.7/app/views/containers/steps/_title.html.erb (7.9ms)
2015-03-26 09:12:15 [I] Rendered /opt/rh/ruby193/root/usr/share/gems/gems/foreman_docker-1.2.0.7/app/views/containers/steps/environment.html.erb within layouts/application (8.1ms)
2015-03-26 09:12:15 [I] Rendered home/_submenu.html.erb (2.0ms)
2015-03-26 09:12:16 [I] Rendered home/_user_dropdown.html.erb (133.5ms)
2015-03-26 09:12:16 [I] Read fragment views/tabs_and_title_records-3 (0.2ms)
2015-03-26 09:12:16 [I] Rendered home/_topbar.html.erb (136.9ms)
2015-03-26 09:12:16 [I] Rendered layouts/base.html.erb (137.9ms)
2015-03-26 09:12:16 [I] Completed 200 OK in 2342ms (Views: 147.2ms | ActiveRecord: 14.6ms)
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.