server_external_events response status is always 'completed' instead of event status which requested as failed
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Undecided
|
Unassigned |
Bug Description
Description
===========
For the server external event rest api response is always completed instead of what the user requested to updated as failed/in-progress .
here the changes required :
https:/
Steps to reproduce
==================
1. POST a rest api request with the status as failed .
2. API response event status will be always completed .
Expected result
===============
Post request :
openstack/
{
"events": [
{
"name": "network-
"tag": "foo",
"server_uuid": "b20f436b-
"status": "failed"
}
]
}
Response :
{
"events": [
{
"tag": "foo",
"name": "network-
"code": 200
}
]
}
Actual result
=============
Post request :
openstack/
{
"events": [
{
"name": "network-
"tag": "foo",
"server_uuid": "b20f436b-
"status": "failed"
}
]
}
Response :
{
"events": [
{
"tag": "foo",
"name": "network-
"code": 200
}
]
}
Changed in nova: | |
status: | Opinion → Won't Fix |
What release is this against? Have you seen this recent change?
https:/ /github. com/openstack/ nova/commit/ e6f742544432d60 66f1fba46665809 19eb7859bd
Also if you're saying that you think because the client posted a 'failed' event but the response contains a 200 for that event, that is working as designed:
https:/ /docs.openstack .org/api- ref/compute/ ?expanded= run-events- detail# run-events
Because the 200 means the event in the request has been processed.