Bug 101106 - gsm_circularity_ck violation when selecting multiple parties to add to Author role
Summary: gsm_circularity_ck violation when selecting multiple parties to add to Author...
Alias: None
Product: Red Hat Enterprise CMS
Classification: Retired
Component: other
Version: nightly
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Archit Shah
QA Contact: Jon Orris
Depends On:
Blocks: 108447
TreeView+ depends on / blocked
Reported: 2003-07-29 04:38 UTC by Dennis Gregorovic
Modified: 2007-04-18 16:56 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2005-11-10 21:00:16 UTC

Attachments (Terms of Use)
acs error report (20.41 KB, text/plain)
2003-07-29 04:39 UTC, Dennis Gregorovic
no flags Details

Description Dennis Gregorovic 2003-07-29 04:38:46 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.0.2) Gecko/20030716

Description of problem:
In the 'content' content section, I went to Roles/Author/Add Member.  I searched
on 'admin'.  This returned a number of results.  I selected 'Account,
Administrator' (the SWA) and 'content Administration Author'.  I then clicked
'Add Members' and got the constraint violation.  I then successfully added the
Account Administrator user by itself.  I did not try any other permutations.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
1.see description

Actual Results:  check constraint violated

Expected Results:  constraint not violated and all parties added to the role

Additional info:

Comment 1 Dennis Gregorovic 2003-07-29 04:39:29 UTC
Created attachment 93213 [details]
acs error report

Comment 2 Richard Li 2003-07-29 18:12:37 UTC
retarget for troika errata; not a regression

Comment 3 Archit Shah 2003-08-27 15:46:32 UTC
the Roles/Author/Add Member UI is adding to the "content Administration Author"
group. So you were actually trying to add a group to itself. The violation is
correct. This is a UI bug. It should be cleaned up to fail better.

Note You need to log in before you can comment on or make changes to this bug.