Red Hat Bugzilla – Bug 803548
Async success notifications pop up from syncs in other orgs
Last modified: 2015-05-04 21:30:46 EDT
Description of problem: Version-Release number of selected component (if applicable): Katello Version: 0.2.13-1.git.3.bd54a84.el6 How reproducible: always Steps to Reproduce: 1. As admin, create an org "myorg", switch to it 2. Create a custom provider/prod/repo (repo large enough to take more than a few seconds to sync) 3. Start the sync of the repo, immediately switch to ACME_Corporation org 4. wait (long enough for the sync to complete - might need to query pulp to find out when it's done) 5. reload the page Actual results: get an async notification about the successful sync of your repo Expected results: No notification Additional info: What's even more bizarre is, if you sync several repos at once, you will eventually get success notifications for all of them. But one at a time. Each new page load will show one new notification. I think these notifications should be removed completely.
fixed in a6846e21a1ad3ff8667d7d18981206e487ac82ed
Verified using: * candlepin-0.7.8-1.el6cf.noarch * candlepin-selinux-0.7.8-1.el6cf.noarch * candlepin-tomcat6-0.7.8-1.el6cf.noarch * katello-1.1.12-7.el6cf.noarch * katello-all-1.1.12-7.el6cf.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.1.8-1.el6cf.noarch * katello-cli-1.1.8-4.el6cf.noarch * katello-cli-common-1.1.8-4.el6cf.noarch * katello-common-1.1.12-7.el6cf.noarch * katello-configure-1.1.9-3.el6cf.noarch * katello-glue-candlepin-1.1.12-7.el6cf.noarch * katello-glue-pulp-1.1.12-7.el6cf.noarch * katello-qpid-broker-key-pair-1.0-1.noarch * katello-qpid-client-key-pair-1.0-1.noarch * katello-selinux-1.1.1-1.el6cf.noarch * pulp-1.1.12-1.el6cf.noarch * pulp-common-1.1.12-1.el6cf.noarch * pulp-selinux-server-1.1.12-1.el6cf.noarch
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2012-1543.html