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.
Reviewed: https:/ /review. opendev. org/c/openstack /cinder/ +/846303 /opendev. org/openstack/ cinder/ commit/ c46d41719e0c819 9dc17ef56641388 9692644ef5
Committed: https:/
Submitter: "Zuul (22348)"
Branch: master
commit c46d41719e0c819 9dc17ef56641388 9692644ef5
Author: Jesper Schmitz Mouridsen <email address hidden>
Date: Fri Jun 17 10:29:00 2022 +0000
Serialize message_* properties of RequestContext
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 deserialization of RequestContext objects.
persist across serialization/
Closes-Bug: 1978729 6bfcb9fdf9fb7a5 5d968ad9f11
Change-Id: Ibdaaf39abafbae
Signed-off-by: Jesper Schmitz Mouridsen <email address hidden>