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):
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
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.
* 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.
Linked to http://projects.theforeman.org/issues/14181
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
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.
Created redmine issue http://projects.theforeman.org/issues/14405 from this bug
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.