condor-low-latency-1.0-10.el5 condor-job-hooks-common-1.0-5.el5 Sending a message into the grid... ... message.getHeaders().setInt("JobUniverse", 5); ... Receiving a response from the grid... (application headers) {...JobUniverse :V2:1:str16(5)... } So type information is lost for attributes sent into the grid, but also attributes set by the grid are all coerced into str16... (application headers) {...ExitCode :V2:1:str16(0),...,ImageSize :V2:4:str16(3784),...,JobDuration :V2:9:str16(45.018719),JobPid :V2:5:str16(26153),JobStartDate :V2:10:str16(1236358349),...,JobStatus :V2:1:str16(4),...}
Int/floats are now correctly set as ints/floats as opposed to all being strings. Fixed in: condor-low-latency-1.0-11
Tested on condor-low-latency-1.0-10 on RHEL5 and it didn't work. Tested on RHEL 5.4/4.8 i386/x86_64 condor-low-latency-1.19 and it works --> VERIFIED
Release note added. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: please see bug summary.
Release note updated. If any revisions are required, please set the "requires_release_notes" flag to "?" and edit the "Release Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. Diffed Contents: @@ -1 +1,8 @@ -please see bug summary.+Grid bug fix + +C: Int/floats were being incorrectly set as strings. +C: Attributes sent into the grid were losing type information. Attributes being set by the grid were all being set to str16. +F: Int/floats are now being set correctly as Int/floats +R: Type information is now correct + +Int/floats were being incorrectly processed, which caused attributes to lose type information, or be set to the incorrect type. Int/floats are now set accurately, and type data is now correct.
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-2009-1633.html