Add request_id to the InstanceAction versioned notifications
As it was agreed on the Rocky PTG [1] it is useful to have the request_id of in the payload of every instance action versioned notification. For example it could help the deployer connect the state change described in the notification with the user action, the request, on the REST API.
So this bp proposes to extend the InstanceActionP
[1] https:/
[2]https:/
Blueprint information
- Status:
- Complete
- Approver:
- Matt Riedemann
- Priority:
- Low
- Drafter:
- Balazs Gibizer
- Direction:
- Approved
- Assignee:
- Zhenyu Zheng
- Definition:
- Approved
- Series goal:
- Accepted for rocky
- Implementation:
-
Implemented
- Milestone target:
-
rocky-2
- Started by
- Matt Riedemann
- Completed by
- Matt Riedemann
Related branches
Related bugs
Sprints
Whiteboard
As noted, this was discussed at the Rocky PTG and had agreement there to do this. -- mriedem 20180305
What about fault and traceback? It also came up in the discussion? - Kevin
The fault and traceback in the versioned error notification can probably just be fixed as a bug since I believe it's a regression in behavior with how the legacy error notifications worked, which just serialized the payload and the exception object was in the payload. I think gibi said he might have had a good reason why the versioned error notification didn't include the traceback, and he was going to investigate it after the PTG. -- mriedem
I will do the investigation and report a bug if needed. -- gibi
Gerrit topic: https:/
Addressed by: https:/
Add request_id filed to InstanceAction versioned notifications
Addressed by: https:/
WIP
Addressed by: https:/
Leave a hint when populate_schema fails
Addressed by: https:/
Move some tests into nova.tests.
