Bugzilla will be upgraded to version 5.0 on a still to be determined date in the near future. The original upgrade date has been delayed.
Bug 248806 - re-activating user doesn't work
re-activating user doesn't work
Product: Red Hat Network
Classification: Red Hat
Component: RHN/Web Site (Show other bugs)
RHN Devel
All Linux
urgent Severity low
: ---
: ---
Assigned To: Grant Gainey
Bret McMillan
Depends On:
Blocks: 239809
  Show dependency treegraph
Reported: 2007-07-18 18:01 EDT by Chris Duryee
Modified: 2007-07-25 11:15 EDT (History)
1 user (show)

See Also:
Fixed In Version: 5.0.2
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-07-25 11:15:19 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Chris Duryee 2007-07-18 18:01:58 EDT
Description of problem:

re-activating disabled users doesn't work in QA

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

How reproducible:

every time

Steps to Reproduce:
1. log in as chris_duryee/redhat
2. try to re-activate beav_subuser
3. error
Comment 1 Grant Gainey 2007-07-19 09:31:21 EDT
Confirmed.  Error from catalina.out is 

2007-07-19 09:28:21,309 [TP-Processor7] ERROR
com.redhat.rhn.frontend.servlets.SessionFilter - Error during transaction.
Rolling back
java.lang.IllegalArgumentException: Could not find ACL handler  user_role in
statement: " user_role(org_admin)". Available ACL handlers: [is, is_solaris,
need_first_user, org_channel_family, org_entitlement, org_is_paying_customer,
org_proxy_evr_at_least, org_role, probe_suite_access, system_feature, uid_role,
user_authenticated, user_can_manage_channels, user_role]

We will need to fix this and get it into stage ASAP, before we hit PROD with 502.
Comment 2 Grant Gainey 2007-07-19 15:52:22 EDT
One-character whitespace error in struts-config.  Sigh
Comment 3 James Bowes 2007-07-25 11:15:19 EDT
rhn502 released.

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