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 there are multiple browser sessions open for the same user, and a promotion fails with "×Failed to promote: Cannot promote a changeset while another is being promoted." (or possibly with other notifs), the notification goes to the wrong session. This only happens for async notifications.
<jsherrill> bbuckingham: jweiss i think this issue is a lot simpler, i think
we can just change synchronous_request to true on that one error
message and be ok
<jsherrill> i think that will fix the bug
Version-Release number of selected component (if applicable):
katello-0.1.77-1.git.8.e67933c.fc14.noarch
How reproducible:
Steps to Reproduce:
1.
2.
3.
Actual results:
Expected results:
Additional info:
Changing to an ehnacement - basically we will have to track notices with sessions to that we can respond to the right session with the right notice. This will have to be a somewhat major rewrite of notifications as it stands now since they aren't tied to sessions at all.
Description of problem: When there are multiple browser sessions open for the same user, and a promotion fails with "×Failed to promote: Cannot promote a changeset while another is being promoted." (or possibly with other notifs), the notification goes to the wrong session. This only happens for async notifications. <jsherrill> bbuckingham: jweiss i think this issue is a lot simpler, i think we can just change synchronous_request to true on that one error message and be ok <jsherrill> i think that will fix the bug Version-Release number of selected component (if applicable): katello-0.1.77-1.git.8.e67933c.fc14.noarch How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: