Description of problem: New roles created automatically in sam 1.3 upgrade Version-Release number of selected component (if applicable): * candlepin-0.8.20-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.20-1.el6sam.noarch * candlepin-tomcat6-0.8.20-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-7.el6sat.noarch * katello-cli-common-1.4.3-7.el6sat.noarch * katello-common-1.4.3-8.el6sam_splice.noarch * katello-configure-1.4.4-2.el6sat.noarch * katello-glue-candlepin-1.4.3-8.el6sam_splice.noarch * katello-glue-elasticsearch-1.4.3-8.el6sam_splice.noarch * katello-headpin-1.4.3-8.el6sam_splice.noarch * katello-headpin-all-1.4.3-8.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 How reproducible: Always Steps to Reproduce: 1. Install SAM 1.2.1 from RHN. Create couple of users and associate them to environments. Do not create any roles though. 2. Run SAM 1.3 upgrade 3. After the upgrade log into SAM Web UI -> Administer -> Roles Actual results: New roles are automatically created - clicking on which an UI user message is thrown (screenshot attached) Expected results: Upgrade should not create new roles. Additional info:
Created attachment 787052 [details] Roles UI error
Created attachment 787053 [details] production.log
Branch: refs/heads/master Home: https://github.com/Katello/katello Commit: 05a575ec64f3569f1275900ae7c4f1e3efb93735 https://github.com/Katello/katello/commit/05a575ec64f3569f1275900ae7c4f1e3efb93735 Author: Tom McKay <thomasmckay> Date: 2013-08-20 (Tue, 20 Aug 2013)
Verified on puddle: http://download.lab.bos.redhat.com/devel/candidate-trees/SAM/SAM-1.3.0-RHEL-6-20130823.1/compose/SAM/x86_64/os/
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