Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 862824 - "Couldn't find all Roles with IDs" error when creating a role
Summary: "Couldn't find all Roles with IDs" error when creating a role
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: WebUI
Version: 6.0.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: Unspecified
Assignee: Tom McKay
QA Contact: Katello QA List
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-03 15:57 UTC by Jeff Weiss
Modified: 2019-09-26 13:36 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-09-19 18:15:54 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Jeff Weiss 2012-10-03 15:57:45 UTC 
Description of problem:


Version-Release number of selected component (if applicable):
CFSE puddle katello-1.1.12-12.el6cf.noarch 

How reproducible:
not very - automated test fails pretty often (~50%), but not reproducible when the server is not under load

Steps to Reproduce:
1. Create a role named "edit-role-1003-095822-300" (but I doubt that the name matters)
2.
3.
  
Actual results:
Fails with "×Couldn't find all Roles with IDs (1, 22, 2, 16, 19, 18, 21, 20) (found 7 results, but was looking for 8)"

Expected results:
Role created

Additional info:
also fails on katello builds
Comment 4 Tom McKay 2012-10-03 18:32:31 UTC 
Note that the role is successfully created but there is some sort of timing issue with, we think, elasticsearch. Investigation will continue.
Comment 5 Jeff Weiss 2012-10-05 12:45:06 UTC 
It seems to be a timing issue where the left pane is loading roles at the same time another session deletes a role.  It could maybe be reproduced using two browsers, clicking delete on one, and then refresh the roles page on the other?
Comment 6 Justin Sherrill 2012-10-05 22:53:52 UTC 
PR issued: https://github.com/Katello/katello/pull/804
Comment 7 Justin Sherrill 2012-10-08 13:08:09 UTC 
So i believe this should fix the issue.  Only time and countless test runs will tell.


f0a303e79f37609722f55c1fbdf4933ac1d4c000
Comment 8 James Laska 2012-10-31 13:31:05 UTC 
What's the status of this issue with regards to the CloudFOrms-1.1 release?  Is this already fixed in downstream CloudForms?
Comment 9 Jeff Weiss 2012-10-31 14:26:10 UTC 
No, it's not fixed in SE and the issue was deemed not important enough to be fixed now.

I agree with that assessment, in order to trigger the problem you need to do 2 pretty specific things in 2 separate sessions at the same time.

It's pretty unlikely a customer would trigger it, and if he did, the error is not severe.  As far as I can tell, the customer can just ignore the error notification and continue.
Comment 10 Mike McCune 2012-10-31 17:53:33 UTC 
moving to 2.0
Comment 12 Mike McCune 2013-09-19 18:15:54 UTC 
These bugs have been resolved in upstream projects for a period of months so I'm mass-closing them as CLOSED:UPSTREAM.  If this is a mistake feel free to re-open.
Note You need to log in before you can comment on or make changes to this bug.