d3097e52b3
The Iddbe50ce0ad3c14562df800bbc09ec5a7e840485 patch only considered instance delete in the happy case when the instance is scheduled to a compute successfully and the compute is available when the delete action is executed. If the instance is never scheduled to a compute or the compute is not available when the instance is deleted legacy delete notifications are emitted from different places, compute.api instead of compute.manager. The original patch missed these places. There will be subsequent patch(es) handling the same edge cases for soft_delete and force_delete. Change-Id: If0693eab2ed31b5fbfe6cbafa5d67b69c2ed8442 Implements: bp versioned-notification-transformation-stein
16 lines
425 B
JSON
16 lines
425 B
JSON
{
|
|
"event_type":"instance.delete.end",
|
|
"payload":{
|
|
"$ref":"common_payloads/InstanceActionPayload.json#",
|
|
"nova_object.data":{
|
|
"block_devices":[],
|
|
"deleted_at":"2012-10-29T13:42:11Z",
|
|
"ip_addresses":[],
|
|
"state":"deleted",
|
|
"terminated_at":"2012-10-29T13:42:11Z"
|
|
}
|
|
},
|
|
"priority":"INFO",
|
|
"publisher_id":"nova-api:fake-mini"
|
|
}
|