Commit 599ee321 authored by Iustin Pop's avatar Iustin Pop
Browse files

Change handling of non-Ganeti errors in jqueue

Currently, if a job execution raises a Ganeti-specific error (i.e.
subclass of GenericError), then we encode it as (error class, [error
args]). This matches the RAPI documentation.

However, if we get a non-Ganeti error, then we encode it as simply
str(err), a single string. This means that the opresult field is not
according to the RAPI docs, and thus it's hard to reliably parse the
job results.

This patch changes the encoding of a failed job (via failure) to always
be an OpExecError, so that we always encode it properly. For the command
line interface, the behaviour is the same, as any non-Ganeti errors get
re-encoded as OpExecError anyway. For the RAPI clients, it only means
that we always present the same type for results. The actual error value
is the same, since the err.args is either way str(original_error);
compare the original (doesn't contain the ValueError):

  "opresult": [
    "invalid literal for int(): aa"


  "opresult": [
        "invalid literal for int(): aa"
Signed-off-by: default avatarIustin Pop <>
Reviewed-by: default avatarMichael Hanselmann <>
parent 4404ffad
......@@ -750,9 +750,10 @@ class _JobQueueWorker(workerpool.BaseWorker):
op.status = constants.OP_STATUS_ERROR
if isinstance(err, errors.GenericError):
op.result = errors.EncodeException(err)
to_encode = err
op.result = str(err)
to_encode = errors.OpExecError(str(err))
op.result = errors.EncodeException(to_encode)
op.end_timestamp = TimeStampNow()"Op %s/%s: Error in opcode %s: %s",
idx + 1, count, op_summary, err)
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment