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:
If a changeset is in the middle of being promoted, user can click through the "Promoting..." text/link to view the changeset and click the "Promote" button again. If something is in the process of being promoted, it makes sense that the button shouldn't be enabled for continued attempts until this one passes/fails
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. Sync RH content
2. Create a new changeset, "Test Changeset"
3. Add content to the changeset; review and Promote content
4. On resulting UI, note "Promoting... Test Changeset"; click this text to view the Changeset details
5. Observe menu bar at bottom; click "Promote"
Actual results:
Button is clickable
Expected results:
Probably should not be clickable if it is already in process.
Additional info:
I am not sure if this can trigger a race condition or not - unsure whether there are safeguards in place to prevent - but it seems it shouldn't be enabled in the first place.