c46d41719e
Change Idc00b125b33b added the ability to store and retrieve user message data in the request context, but it neglected to add code to make sure they would persist across serialization and deserialization of the request context object, as happens in the create-backup workflow. As a result, when a user message needed to be created to describe an error condition in the backup driver, instead we'd get an exception raised: "TypeError: 'NoneType' object is not subscriptable". This patch fixes the issue by making sure the message_* properties persist across serialization/deserialization of RequestContext objects. Closes-Bug: 1978729 Change-Id: Ibdaaf39abafbae6bfcb9fdf9fb7a55d968ad9f11 Signed-off-by: Jesper Schmitz Mouridsen <jesper@schmitz.computer>
9 lines
355 B
YAML
9 lines
355 B
YAML
---
|
|
fixes:
|
|
- |
|
|
`Bug #1978729 <https://bugs.launchpad.net/cinder/+bug/1978729>`_: Fixed
|
|
context.message_action is None on errors by backup drivers. The message_*
|
|
properties of the context were not passed during rpc, which caused a double
|
|
exception when a backup driver raised an exception, masking the actual backup
|
|
driver exception.
|