Hide Forgot
Description of problem: Submit job with limit Open Cumin web: Grid - Limits - Save to CSV file Result: Name Current usage Max allowance testlimit 1 <a href="form.html?modes.m=NegotiatorLimitTask_54703184;modes.NegotiatorLimitTask_54703184.return=csv%3Ffile%3DLimit%3Bmodes.m%3Dlimits_csv" >1.0</a> Version-Release number of selected component (if applicable): cumin-0.1.5233-1.el6.noarch How reproducible: 100% Steps to Reproduce: 1. Submit job with limit 2. Open Cumin web: 3. Grid - Limits - Save to CSV file Actual results: CSV contains html metadata Expected results: CSV contains proper values Additional info:
I'll take a look at this too.
(In reply to comment #2) > I'll take a look at this too. I'm on it. Should have it fixed soon.
Fixed on trunk revision 5247
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 class that renders the limits did not have special handling for the CSV export. Consequence: The exported version of the limits table showed HTML markup when it is not appropriate. Fix: Added special handling to strip out the html tagging on CSV export. Result: The limits now display correctly in the exported CSV file.
The 'Fixed In Version' field states that this bug was fixed in cumin-0.1.5251-1, but I was able to reproduce it in cumin-0.1.5444-3. Was it originally fixed in cumin-0.1.5251-1, but then removed from later builds, and then added again? If so, could you please update the 'Fixed In Version' field so that I can finish verification?
Yes, it was descoped for the last release which was built from a branch rather than trunk. Latest builds have the fix. Note that the svn revision numbers apply to the entire Cumin repo, so it is possible to have features missing from a release even when the release has a higher revision number than the commit that originally fixed the issue :) (In reply to comment #12) > The 'Fixed In Version' field states that this bug was fixed in > cumin-0.1.5251-1, but I was able to reproduce it in cumin-0.1.5444-3. > > Was it originally fixed in cumin-0.1.5251-1, but then removed from later > builds, and then added again? If so, could you please update the 'Fixed In > Version' field so that I can finish verification?
I was able to reproduce on cumin-0.1.5192-4 I verified on RHEL5 and RHEL6, both i386 and x86_64, with cumin-0.1.5572-1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. http://rhn.redhat.com/errata/RHSA-2013-0564.html