Bug 1012609

Summary: Duplicate key value error while logging back in to SAM after timed out in ldap mode
Product: [Retired] Subscription Asset Manager Reporter: sthirugn <sthirugn>
Component: katelloAssignee: Tom McKay <tomckay>
Status: CLOSED ERRATA QA Contact: SAM QE List <sam-qe-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: NightlyCC: bkearney, tomckay
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-10-01 10:47:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 833466    

Description sthirugn@redhat.com 2013-09-26 17:47:26 UTC 
Description of problem:
Unable to log back in to SAM after timed out in ldap mode

Version-Release number of selected component (if applicable):
* candlepin-0.8.26-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.26-1.el6sam.noarch
* candlepin-tomcat6-0.8.26-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-11.el6sat.noarch
* katello-cli-common-1.4.3-11.el6sat.noarch
* katello-common-1.4.3-16.el6sam_splice.noarch
* katello-configure-1.4.4-5.el6sam.noarch
* katello-glue-candlepin-1.4.3-16.el6sam_splice.noarch
* katello-glue-elasticsearch-1.4.3-16.el6sam_splice.noarch
* katello-headpin-1.4.3-16.el6sam_splice.noarch
* katello-headpin-all-1.4.3-16.el6sam_splice.noarch
* katello-selinux-1.4.4-2.el6sat.noarch
* thumbslug-0.0.34-1.el6sam.noarch
* thumbslug-selinux-0.0.34-1.el6sam.noarch

How reproducible:
Always

Steps to Reproduce:
1. Install ldap with free_ipa
2. Log in to UI and leave the UI until time out
3. After time out, try logging back in

Actual results:
UI shows an error (as shown below): (Screenshot attached)
ERROR: duplicate key value violates unique constraint "index_roles_users_on_user_id_and_role_id" (PGError)
Click here for more details.

Expected results:
No error

Additional info:
Comment 3 sthirugn@redhat.com 2013-09-26 17:57:03 UTC 
Correction: I am able to log in.  But I see the UI error (and error in the logs) for each action.
Comment 4 sthirugn@redhat.com 2013-09-26 21:43:13 UTC 
So far I faced this in the following ldap modes:
1. free_ipa
2. Active Directory
Comment 5 Tom McKay 2013-09-27 14:36:09 UTC 
Branch: refs/heads/master
  Home:   https://github.com/Katello/katello
  Commit: 870a2b4539d9f79cc7061452f782bd08483efe98
      https://github.com/Katello/katello/commit/870a2b4539d9f79cc7061452f782bd08483efe98
  Author: Tom McKay <thomasmckay>
  Date:   2013-09-27 (Fri, 27 Sep 2013)
Comment 8 sthirugn@redhat.com 2013-09-30 19:26:10 UTC 
Version Tested:
* candlepin-0.8.26-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.26-1.el6sam.noarch
* candlepin-tomcat6-0.8.26-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-11.el6sat.noarch
* katello-cli-common-1.4.3-11.el6sat.noarch
* katello-common-1.4.3-18.el6sam_splice.noarch
* katello-configure-1.4.4-5.el6sam.noarch
* katello-glue-candlepin-1.4.3-18.el6sam_splice.noarch
* katello-glue-elasticsearch-1.4.3-18.el6sam_splice.noarch
* katello-headpin-1.4.3-18.el6sam_splice.noarch
* katello-headpin-all-1.4.3-18.el6sam_splice.noarch
* katello-selinux-1.4.4-2.el6sat.noarch
* thumbslug-0.0.34-1.el6sam.noarch
* thumbslug-selinux-0.0.34-1.el6sam.noarch
Comment 10 errata-xmlrpc 2013-10-01 10:47:05 UTC 
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/RHBA-2013-1394.html