Bug 635197

Created attachment 448154 [details]
Max Allowance Screenshot

Fixed in revision 4646.

Field now displays as float since Max Allowance limit in condor is a float.  Values above 1000000 render as "Unlimited"

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause
    The Max Allowance limit value for a submission displayed as an integer even though the value is a float.  Additionally, the default value for this limit intended to give "unlimited" behavior rendered as its explicit value.  Consequently, the sense of "unlimited" was not communicated to the user.

Consequence
    (see above).

Fix
    Changed the value to render as a float rather than an integer.  Render values over 1000000 as "Unlimited".

Result
    If the Max Allowance limit is set to a floating point value, that value will be accurately reflected in the table. Submissions with a default Max Allowance value or a very large Max Allowance value will display with a Max Allowance value of "Unlimited".

Verified on cumin-0.1.4654-1.el5

CONCURRENCY_LIMIT_DEFAULT was unset during verification
and following shell script was run:
----------------------------------------------
getent passwd test || adduser test
echo Submitting a job
su - test -c "condor_submit $* << EOF
Executable     = /bin/sleep
Universe = vanilla
concurrency_limits = REALLYNOLIMIT
args    = 20m
queue 1
EOF"

    Technical note updated. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    Diffed Contents:
@@ -1,11 +1,11 @@
-Cause
-    The Max Allowance limit value for a submission displayed as an integer even though the value is a float.  Additionally, the default value for this limit intended to give "unlimited" behavior rendered as its explicit value.  Consequently, the sense of "unlimited" was not communicated to the user.
+C: The Max Allowance limit value for a submission displayed as an integer even though the value is a float.  Additionally, the default value for this limit intended to give "unlimited" behavior rendered as its explicit value.  Consequently, the sense of "unlimited" was not communicated to the user.
 
-Consequence
-    (see above).
+C: (see above).
 
-Fix
-    Changed the value to render as a float rather than an integer.  Render values over 1000000 as "Unlimited".
+F: Changed the value to render as a float rather than an integer.  Render values over 1000000 as "Unlimited".
 
-Result
+R: If the Max Allowance limit is set to a floating point value, that value will be accurately reflected in the table. Submissions with a default Max Allowance value or a very large Max Allowance value will display with a Max Allowance value of "Unlimited".
-    If the Max Allowance limit is set to a floating point value, that value will be accurately reflected in the table. Submissions with a default Max Allowance value or a very large Max Allowance value will display with a Max Allowance value of "Unlimited".+
+Release Note Entry:
+
+Previously, the value for "Max Allowance" in Cumin was incorrectly displayed as an integer despite being a float value and "unlimited" was assigned as the default value instead of assigned to a specific limit. The "Max Allowance" value is correctly displayed as a float value and the "unlimited" value is now only assigned to values over 1,000,000.

An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.

http://rhn.redhat.com/errata/RHEA-2011-0889.html