Add the full traceback to the ExceptionPayload used in the error versioned notifications
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:/
[2] https:/
[3] http://
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:
-
rocky-3
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
There was agreement in today's nova meeting to approve this specless blueprint. -- mriedem 20180315
Gerrit topic: https:/
Addressed by: https:/
Add full traceback to ExceptionPayload in versioned notifications
