Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 885750

Summary: Button 'Change percentage' displayed incorrectly in dynamic quota editing dialog
Product: Red Hat Enterprise MRG Reporter: Peter Belanyi <pbelanyi>
Component: cuminAssignee: grid-maint-list <grid-maint-list>
Status: CLOSED WONTFIX QA Contact: MRG Quality Engineering <mrgqe-bugs>
Severity: unspecified Docs Contact:
Priority: low    
Version: DevelopmentCC: athomas, croberts, matt, sgraf, tmckay
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-05-26 20:17:26 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Screenshot of Change percentage button none

Description Peter Belanyi 2012-12-10 14:40:20 UTC
Created attachment 660904 [details]
Screenshot of Change percentage button

Description of problem:
Button 'Change percentage' displayed incorrectly in dynamic quota editing dialog

Version-Release number of selected component (if applicable):
cumin-0.1.5564-1
Firefox 10.0.5 (Mozilla/5.0 (X11; Linux x86_64; rv:10.0.5) Gecko/20120601 Firefox/10.0.5)

How reproducible:
100%

Steps to Reproduce:
1. Set up condor to have dynamic quotas
2. Go to Grid / Quotas cumin page
3. Click on a dynamic quota value to edit it

Actual results:
Dialog 'Edit Dynamic Group Quota' displays button 'Change percentage' incorrectly (there is some garbage on the right side of the button)

Expected results:
Button displayed correctly

Additional info:

Comment 1 Trevor McKay 2013-01-29 19:40:32 UTC
Can't reproduce this on RHEL6 with latest cumin.

User agent string reports the same Firefox as above.

Comment 5 Anne-Louise Tangring 2016-05-26 20:17:26 UTC
MRG-Grid is in maintenance and only customer escalations will be considered. This issue can be reopened if a customer escalation associated with it occurs.