Actions
Bug #11148
open[Crunch2] Propagate dispatch error messages (e.g., sbatch fails) to user via logs/websocket
Story points:
-
Release:
Release relationship:
Auto
Description
Background¶
If crunch-dispatch-slurm encounters an error while trying to submit a container to the slurm queue, it logs a message to stderr, but there is no way for a user to see this. If the error persists, the user has no way of knowing whether anything is happening.
Fix¶
In addition to printing a message on stderr, crunch-dispatch-slurm should use the Arvados API to emit a log that is visible to the user.- object_uuid: container uuid
- event_type: "dispatch"
Similar to source:services/crunch-run/logging.go#L183
A log should also be emitted when the container is successfully submitted to the slurm queue.
Updated by Tom Morris over 7 years ago
- Target version set to Arvados Future Sprints
Updated by Ward Vandewege over 3 years ago
- Target version deleted (
Arvados Future Sprints)
Actions