Previously whenever you called system.tasks all tasks from candlepin were duplicated within the db every time. It was not checking properly that the tasks already existed. https://github.com/Katello/katello/pull/2784
Branch: refs/heads/master Home: https://github.com/Katello/katello Commit: 64afe910353076200f6831e9ad1014c335686bd7 https://github.com/Katello/katello/commit/64afe910353076200f6831e9ad1014c335686bd7 Author: Justin Sherrill <jsherril> Date: 2013-08-20 (Tue, 20 Aug 2013)
Lates build (Snap4) should contain these fixes. Please test on Snap4.
VERIFIED. Steps for verification: 1. Installed SAM 1.2.1. Registered a client, added subscription, removed subscription. See the attached sam 1.2.1 observed error screenshot. Everytime a system event happened, the events were duplicated 2. Installed SAM 1.3. Repeated the same steps as above and did not get any duplicates. See the attached sam 1.3 verification sreenshot. Version Tested: Version Tested: * candlepin-0.8.24-1.el6sam.noarch * candlepin-scl-1-5.el6_4.noarch * candlepin-scl-quartz-2.1.5-5.el6_4.noarch * candlepin-scl-rhino-1.7R3-1.el6_4.noarch * candlepin-scl-runtime-1-5.el6_4.noarch * candlepin-selinux-0.8.24-1.el6sam.noarch * candlepin-tomcat6-0.8.24-1.el6sam.noarch * elasticsearch-0.19.9-8.el6sat.noarch * katello-candlepin-cert-key-pair-1.0-1.noarch * katello-certs-tools-1.4.2-2.el6sat.noarch * katello-cli-1.4.3-9.el6sat.noarch * katello-cli-common-1.4.3-9.el6sat.noarch * katello-common-1.4.3-11.el6sam_splice.noarch * katello-configure-1.4.4-3.el6sat.noarch * katello-glue-candlepin-1.4.3-11.el6sam_splice.noarch * katello-glue-elasticsearch-1.4.3-11.el6sam_splice.noarch * katello-headpin-1.4.3-11.el6sam_splice.noarch * katello-headpin-all-1.4.3-11.el6sam_splice.noarch * katello-selinux-1.4.4-2.el6sat.noarch * thumbslug-0.0.32-1.el6sam.noarch * thumbslug-selinux-0.0.32-1.el6sam.noarch
Created attachment 792219 [details] sam 1.2.1 observed error
Created attachment 792220 [details] sam 1.3 verification
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/RHEA-2013-1390.html