Bugzilla – Bug 6134
GT4.2 RC2: error reporting in globusrun-ws
Last modified: 2008-06-09 12:18:05
You need to
before you can comment on or make changes to this bug.
globusrun-ws does not print all the nice explanations when e.g. a job
with staging fails due to an error in staging, but it did so in 4.0.x.
Gram4 in trunk puts all the fault information into the notification
message, as it did in 4.0.x. But due to changes in fault handling,
the fault causes are all nested, not arranged in an array.
(See "Faults" in
It looks like globusrun-ws grabs the description of the top-level fault
and ignores the descriptions in the nested FaultCauses.
I'll mark it critical, maybe it's a blocker.
I'll add links where to find examples, because attachments are disabled.
Here are the examples:
invalid count element:
Seems like we finally agreed, that globusrun-ws just has to look at the
description of a fault, and not dive into the fault causes to get more
In case of an RFT error, Gram on the server-side will pull RFT's fault
description and add it to the fault description of the fault of the job.
committed, will be in 4.2.0