Fix 'null' response on router-interface-remove operation
To avoid a 'null' response body, the delete operation returns a response
that is consistent with its add counterpart, i.e. we return the router
id with details about the interface being affected by the operation, as
well as the tenant id.
A unit test is added to ensure that the right body is returned and minor
adjustments have been made to the plugins affected by the change.
Long-term, a delete operation should really return 204 w/o a body, but
this requires some major rework of the WSGI handling within Quantum.
This is an interim solution that deals with an 'ugly' response body,
whilst keeping backward compatibility.
Reviewed: https:/ /review. openstack. org/27868 github. com/openstack/ quantum/ commit/ 2516c136549195a 92a20aa6570e27a f5dfbef28a
Committed: http://
Submitter: Jenkins
Branch: master
commit 2516c136549195a 92a20aa6570e27a f5dfbef28a
Author: armando-migliaccio <email address hidden>
Date: Tue Apr 30 16:19:04 2013 -0700
Fix 'null' response on router- interface- remove operation
To avoid a 'null' response body, the delete operation returns a response
that is consistent with its add counterpart, i.e. we return the router
id with details about the interface being affected by the operation, as
well as the tenant id.
A unit test is added to ensure that the right body is returned and minor
adjustments have been made to the plugins affected by the change.
Long-term, a delete operation should really return 204 w/o a body, but
this requires some major rework of the WSGI handling within Quantum.
This is an interim solution that deals with an 'ugly' response body,
whilst keeping backward compatibility.
Fixes bug 1173284
Change-Id: Icaab87ad0c8561 c0690c8f0a14db8 15d8886bc71