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.
Description of problem:
When creating a new container that requires a Docker image to be
pulled down into the compute resource (e.g. choosing either the
'Docker Hub' or external 'Registry' and typing the name of an image
that is not yet present in the compute resource), there's no visual
information to the end user that something is happening and you're
only redirected to the new container page once the image is pulled
down. We need to handle this scenario the same way that we handle
provisioning hosts and display progress like the orchestration
progress bar displayed during host creation.
Please refer to https://bugzilla.redhat.com/show_bug.cgi?id=1204925
Version-Release number of selected component (if applicable):
* Satellite-6.1.0-RHEL-7-20150324.0
How reproducible:
Steps to Reproduce:
1. Create a Docker-based compute resource
2. Create a New Container and choose the Docker Hub tab after selecting your compute resource
3. Type 'wordpress' then click the search button (magnifying glass icon) to trigger a fetch to Docker Registry
4. Select a valid Tag and complete the wizard
Actual results:
Upon finishing the wizard, the user is not taken to the new container page until the 'wordpress' image is pulled down onto the computer resource.
Expected results:
* The user should be taken immediately to the new container page.
* The 'Power On' button should be disabled until the docker image has been pulled and is ready.
Additional info:
Comment 2Daniel Lobato Garcia
2016-03-14 12:04:53 UTC
Moving to POST since upstream bug http://projects.theforeman.org/issues/14181 has been closed
-------------
Daniel Lobato Garcia
Applied in changeset commit:foreman-docker|9ea405911cef1f02ca42db77c16bea4fe297093e.
I still do not see any type of visual indication that something is happening when I attempt to follow the original steps mentioned here.
Failed on Satellite 6.2.0 SNAP 5.1
Comment 5Daniel Lobato Garcia
2016-03-31 06:33:21 UTC
Actually this ticket is linked to the wrong redmine - my bad. The current redmine ticket should be linked to https://bugzilla.redhat.com/show_bug.cgi?id=1230710 instead.
I'll create a new redmine for this.
Comment 6Daniel Lobato Garcia
2016-03-31 06:33:36 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.