Bug 1190229 - Changing tabs on New container wizard deselects external hub already selected
Summary: Changing tabs on New container wizard deselects external hub already selected
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Container Management
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Daniel Lobato Garcia
QA Contact: Katello QA List
URL: http://projects.theforeman.org/issues...
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-02-06 17:38 UTC by Elyézer Rezende
Modified: 2017-01-11 20:44 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-11 20:44:06 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 10197 0 None None None 2016-04-22 15:44:10 UTC

Description Elyézer Rezende 2015-02-06 17:38:17 UTC 
Description of problem:
In the second step on the New Container wizard, if you select the "External registry" tab and a Registry, if you go to "Docker hub" tab and then go back on the "External registry" tab the previous state of Registry is lost.


Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150205.0

How reproducible:
Aways

Steps to Reproduce:
1. Containers > New Container
2. Select a Docker Compute resource and proceed to next step
3. Select External registry tab and select an already created registry.
4. Go to the Docker hub tab
5. Go back to the External registry tab

Actual results:
The previous selected Registry is cleaned


Expected results:
The previous selected registry remains when changing tabs


Additional info:
Comment 2 Bryan Kearney 2015-04-17 20:23:45 UTC 
Created redmine issue http://projects.theforeman.org/issues/10197 from this bug
Comment 3 Bryan Kearney 2015-08-25 18:33:28 UTC 
Upstream bug component is Container Management
Comment 4 Bryan Kearney 2017-01-11 20:44:06 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.
Note You need to log in before you can comment on or make changes to this bug.