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 129287 - 500 error for systems if mon_admin user is not org_admin.
500 error for systems if mon_admin user is not org_admin.
Status: CLOSED DUPLICATE of bug 129291
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Monitoring (Show other bugs)
All Linux
medium Severity medium
: ---
: ---
Assigned To: Kim Dykeman
Fanny Augustin
Depends On:
  Show dependency treegraph
Reported: 2004-08-05 18:09 EDT by Kim Dykeman
Modified: 2007-06-20 16:11 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 14:04:58 EST
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 Kim Dykeman 2004-08-05 18:09:44 EDT
Description of problem:

A Monitoring admin can view a list of user's notification methods.
This list has links to Users and notification methods; however, the
ability to view/edit these is currently restricted to org_admins so
clicking on either of these links results in a 500 if the monitoring
admin is not an org_admin. 

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


How reproducible:


Steps to Reproduce:
1. As a monitoring admin that is not also an org admin, click on the
top-level monitoring tab.

2. Click on the link for a system or a probe that the user doesn't
have permission for.

Actual results:

500 Error.

Expected results:

One would expect to arrive at the system details page or the probe
details page.

Additional info:
Comment 1 Kim Dykeman 2004-08-05 18:27:34 EDT
I'm closing this one since I intermixed the description of two
seperate bugs.  I opened the following bugs in it's stead:

bug 129291
bug 129292

*** This bug has been marked as a duplicate of 129291 ***
Comment 2 Red Hat Bugzilla 2006-02-21 14:04:58 EST
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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