Bug 1360190 - Editing tags for a group results in "Unexpected error encountered"
Summary: Editing tags for a group results in "Unexpected error encountered"
Keywords:
Status: CLOSED DUPLICATE of bug 1360911
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: UI - OPS
Version: 5.5.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.7.0
Assignee: Zita Nemeckova
QA Contact: Niyaz Akhtar Ansari
URL:
Whiteboard: retest:tag:ui:error
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-07-26 08:10 UTC by Peter McGowan
Modified: 2019-12-16 06:12 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-01 18:25:17 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
Production log showing the error with stack trace (13.08 KB, text/plain)
2016-07-28 10:59 UTC, klaus.wagner
no flags Details

Description Peter McGowan 2016-07-26 08:10:16 UTC
Description of problem:
Depending on how we access a group in the WebUI, trying to edit the tags results in an "Unexpected error encountered" error.

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

How reproducible:
Every time


Steps to Reproduce:
1. In Configure -> Configuration -> Access Control -> Users, pick a user.
2. In the right-hand pane, click on the user's group to navigate to the group details
3. Attempt to edit the group's tags by clicking Policy -> Edit Tags for this group

Actual results:
Unexpected error encountered, Error text: Couldn't find User with 'id=1000000002880[ops/x_button]

Expected results:
The group's tags should be presented

Additional info:
This only seems to happen if we navigate to the group from the user's details.

Comment 2 Harpreet Kataria 2016-07-27 13:47:59 UTC
Zita,

Can you take a look at this one, seems to be setting incorrect class to find a record when going to group from User details screen.

Thanks,
~Harpreet.

Comment 3 Zita Nemeckova 2016-07-27 14:08:40 UTC
Hi,

I cannot reproduce on master. Please give me your appliance. Thanks :)

Comment 4 Dave Johnson 2016-07-27 21:42:53 UTC
Niyaz, can you reproduce this in 5.5.5 or 5.6.1?  THX!    If not, I believe we want to close this as CURRENTRELEASE

Comment 5 Niyaz Akhtar Ansari 2016-07-28 07:00:31 UTC
Dave,

The bug is not reproduceable in 5.5.5 and 5.6.1 .It is working fine.

Thanks,
~Niyaz

Comment 6 Peter McGowan 2016-07-28 07:28:59 UTC
I can confirm that the bug DOES also affect our production system running 5.5.5, but not our test system running 5.5.5.

One of the significant differences between the two are the number of users (227), groups(3601) and tags (around 7500ish) in production.

Comment 8 klaus.wagner 2016-07-28 10:58:59 UTC
Hi,

we are working with Peter McGowan on this issue (our system is affected by this)

As requested I added a section of the production log showing the error.
We don't think we can provide a database export as this contains confidential information.

br, Klaus Wagner

Comment 9 klaus.wagner 2016-07-28 10:59:49 UTC
Created attachment 1185023 [details]
Production log showing the error with stack trace

Comment 10 klaus.wagner 2016-07-28 11:05:19 UTC
We also noticed in the logs that there is a WARNING regarding exceeding the memcached size limit:

WARN -- : Value for MIQ:VMDB:ffdf1936fe7af187bfcd0908f6e98835 over max size: 1048576 <= 1627073

This could be related to the following bug (also an environment with a very high number of tags):

https://bugzilla.redhat.com/show_bug.cgi?id=1360911

Comment 12 Martin Hradil 2016-08-01 18:25:17 UTC

*** This bug has been marked as a duplicate of bug 1360911 ***


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