Bug 697857

Summary: Reports->Configuration History: Delete button is disabled for a user having configure write permission
Product: [Other] RHQ Project Reporter: Sunil Kondkar <skondkar>
Component: Core UIAssignee: RHQ Project Maintainer <rhq-maint>
Status: CLOSED WONTFIX QA Contact: Corey Welton <cwelton>
Severity: unspecified Docs Contact:
Priority: medium    
Version: 4.0.0CC: hrupp, jshaughn
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-04-19 16:30:47 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---
Bug Depends On:    
Bug Blocks: 585306    

Description Sunil Kondkar 2011-04-19 13:10:44 UTC
Description of problem:
Delete button is disabled for a user having configure write permission in Reports->Configuration History page.

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

build#1144 (Version: 4.0.0-SNAPSHOT Build Number: 50f58a4)

How reproducible:


Steps to Reproduce:

1. Login to RHQ as rhqadmin.
2. Create a user and a compatible group of resources (Ex: RHQ Agent).
3. Create a role with only configure write resource permissions.
4. Assign the resource group and the user created to the role.
5. Logout and login as the user created above( with only configure write resource permissions)
6. Navigate to Reports->Configuration History.
7. Select a row and observe that the 'Delete' button is disabled.
Actual results:

The Delete button is disabled for a user having configure write permission.

Expected results:

The 'Delete' button should be enabled after selecting a config history and user should be able to delete resource config history in reports.

Additional info:

When the same user (with only configure_write resource permissions) navigates to the 'Configuration->History' tab of the resource, the 'Delete' button is enabled and user can delete the config history.

Comment 1 Jay Shaughnessy 2011-04-19 16:30:47 UTC
The subsystem views are cross-inventory views and currently often require a
global priv (manage_inventory) to enable buttons that perform "write"
operations.  The alternative is a costly button enable check that requires
resource level perm checking each time the selection changes.  We've opted not
to do that in these views at this time.

This could be re-opened as an RFE based on customer demand.