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:
I didn't get a screenshot of the error message, I will attach it if I ever see it again.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Sync some RH content
2. Create a new system template
3. Add some packages and package groups to the system template; save
4. Add another package to the system template; do /not/ save.
5. Bring up the download menu and hit the Download button
Actual results:
Current results:
Dialogue box:
The current template "Test System Template" has been modified. If you leave, any changes will be lost."
Are you sure you want to leave this page?
Clicking "Leave" allows user to download (the old, saved) template
Clicking "Stay" returns user to view
*sometimes*, doing one of these returns an error about being unable to retrieve template and indicates user needs to reload page.
Expected results:
* We're not really naving away from an unsaved template, so probably shouldn't see the message
* Not sure if we should be allowed to download the unsaved template - probably not.
Additional info:
agree with you corey, we shouldn't really allow you to download a modified template. Would the user expect to download the modified or unmodified version?
To fix it, i disabled the download button if the template is modified. To make it clear what's going on, I added a tipsy that only is enabled when the button is downloaded for this reason.
d29586a2f079c75e05df9e233a69d03cc0d6f5c3
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM. If this is a mistake feel free to re-open.