Add the full traceback to the ExceptionPayload used in the error versioned notifications

Registered by Balazs Gibizer on 2018-03-13

On the Rocky PTG it was discussed [1] that external tools consuming notifications want to see the full traceback in the error notifications.

During the original versioned notification spec review [2] there was an agreement not to add the full traceback to the ExceptionPayload. The main reasons was that it cannot be well defined what goes in that field (it would have been a
single serialized string) and possible security implications.

The instance-action REST API has already provide the traceback to the user (to the admin by default) and the notifications are also admin only things as they are emitted to the message bus by default. So I assume that security is not a bigger concern for the notification than for the REST API.

On the ML [3] post there was no objection to add new string field to the ExceptionPayload that will hold the serialized traceback object.

[1] L387 in https://etherpad.openstack.org/p/nova-ptg-rocky
[2] https://review.openstack.org/#/c/286675/
[3] http://lists.openstack.org/pipermail/openstack-dev/2018-March/128105.html

Blueprint information

Status:
Complete
Approver:
Matt Riedemann
Priority:
Medium
Drafter:
Balazs Gibizer
Direction:
Approved
Assignee:
Zhenyu Zheng
Definition:
Approved
Series goal:
Accepted for rocky
Implementation:
Implemented
Milestone target:
milestone icon rocky-3
Started by
Matt Riedemann on 2018-05-29
Completed by
Matt Riedemann on 2018-06-19

Related branches

Sprints

Whiteboard

There was agreement in today's nova meeting to approve this specless blueprint. -- mriedem 20180315

Gerrit topic: https://review.openstack.org/#q,topic:bp/add-full-traceback-to-error-notifications,n,z

Addressed by: https://review.openstack.org/564092
    Add full traceback to ExceptionPayload in versioned notifications

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.

Subscribers

No subscribers.