2a0f2a0d27
This patch adds full traceback to ExceptionPayload in versioned notifications. The instance fault field and instance-action REST API has already provide the traceback to the admin users (controlable through policy) and the notifications are also admin only things as they are emitted to the message bus by default. So it is assumed that security is not a bigger concern for the notification than for the REST API. On the ML [1] post there was no objection to add new string field to the ExceptionPayload that will hold the serialized traceback object. [1] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128105.html Implements: blueprint add-full-traceback-to-error-notifications Change-Id: Id587967ea4f9980c292492e2f659bf55fb037b28
23 lines
927 B
JSON
23 lines
927 B
JSON
{
|
|
"event_type": "instance.volume_attach.error",
|
|
"payload": {
|
|
"$ref": "common_payloads/InstanceActionVolumePayload.json#",
|
|
"nova_object.data": {
|
|
"fault": {
|
|
"nova_object.data": {
|
|
"exception": "CinderConnectionFailed",
|
|
"exception_message": "Connection to cinder host failed: Connection timed out",
|
|
"function_name": "attach_volume",
|
|
"module_name": "nova.tests.functional.notification_sample_tests.test_instance",
|
|
"traceback": "Traceback (most recent call last):\n File \"nova/compute/manager.py\", line ..."
|
|
},
|
|
"nova_object.name": "ExceptionPayload",
|
|
"nova_object.namespace": "nova",
|
|
"nova_object.version": "1.1"
|
|
}
|
|
}
|
|
},
|
|
"priority": "ERROR",
|
|
"publisher_id": "nova-compute:compute"
|
|
}
|