Bug #11148

Updated by Tom Clegg over 4 years ago

h3. 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.

h3. 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