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 a user attempts to apply a GPG key to an entire product, the key is saved immediately, once user hits "Save". A confirmation screen then pops up afterwards, to assure user wants to do this. This confirmation screen of course does nothing - the change has already been saved.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Create a third-party provider with multiple products and repos
2. Create a gpg key
3. Content > Repositories > Provider > $provider
4. Within the provider details, click on a product name
5. In edit products, select the key you created, through the "GPG key" dropdown, and hit save.
6. Note the UI notification that the product has changed; also note the confirmation screen that appears afterwards.
7. hit "No" on the confirmation screen
8. Navigate back to you provider from the UI (repeat steps 3-4)
Actual results:
GPG information is saved; even if user hits "No" on the confirmation, details have already been updated.
Expected results:
We should be seeing the confirmation screen before user can ever "Save"; if user hits "No", no changes should be made.
Additional info:
CloudForms System Engine Version: 1.1.12-22.el6cf
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.