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-04 17:54:15 UTC
Description of problem:
When navigating forward and then backward in the New Container wizard, the status of a selected Katello image is not stored and all changes already made are lost.
Version-Release number of selected component (if applicable):
Satellite-6.1.0-RHEL-7-20150303.0
How reproducible:
Aways
Steps to Reproduce:
1. Go to New Container wizard, select an already created Docker-based compute resource
2. On the next step, fill all information on the Katello tab
3. Go to next step
4. Go back to the previous step and all filled information will be lost
Actual results:
Katello image information state is not being persisted
Expected results:
All already filled Katello image information should be restored when coming back to the image step.
Additional info:
Comment 7Daniel Lobato Garcia
2016-09-12 09:30:55 UTC
This bz has been moved to an upstream issue. We will no longer be tracking this in the downstream. When the upstream issue is fixed, the next release of Satellite will include the fix. If this is a concern, please reach out to Bryan Kearney or Rich Jerrido. Thank you.