Spike: Investigate NPE causing workflow failure
See original GitHub issueVersion: Cromwell v38 Backend: PAPI v2
Running a hello world workflow on Pipelines API v2 against inputs originating from a Requester Pays bucket.
The job finishes running, generates a 0 return code and detritus logs (stdout/stderr). However the workflow failures with an error message (full message attached). failed-workflow-metadata.txt
Unable to complete JES Api Request. Caught NPE while processing operation projects/dvoet-prod-test-20190305-3/operations/11506961050484846699
Searched the code and found the error here: https://github.com/broadinstitute/cromwell/blob/2d8ff3b0962bbe84828445fd3ac77d2379e499c2/supportedBackends/google/pipelines/v2alpha1/src/main/scala/cromwell/backend/google/pipelines/v2alpha1/api/request/GetRequestHandler.scala#L49-L83
Operation metadata attached as well. operation-metadata.yaml.txt
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (4 by maintainers)
Top GitHub Comments
We have also found 2000/2000 workflows failed due to this issue
Unable to complete JES Api Request. Caught NPE while processing...
today. We are using cass-prod"cromwell": "36-fde91e6"
, and the Cromwell hasn’t been changed for at least ~2 weeksClosing this as the real fix is filed here: https://github.com/broadinstitute/cromwell/issues/4774