Description of problem: DELETE request content is -- url:/api/vms/a4b7e68f-6d91-4bd6-bc12-044a5dae28b5/watchdogs/00000000-0000-0000-0000-000000000000 Failed to delete element NOT as expected: Status: 500 Reason: Internal Server Error Version-Release number of selected component (if applicable): 3.6.0-4 vdsm-4.17.0-1201.git7ba0684.el7.noarch How reproducible: 100% Steps to Reproduce: 1.DELETE request content is -- url:/api/vms/a4b7e68f-6d91-4bd6-bc12-044a5dae28b5/watchdogs/00000000-0000-0000-0000-000000000000 2. 3. Actual results: Status: 500 Reason: Internal Server Error Expected results: the watchdog device should delete Additional info:
please attach engine log
Created attachment 1059380 [details] rhevm logs adding the logs. and also link of the test : https://rhev-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/3.6-GE-Tier0/64/testReport/junit/rhevmtests.sla.watchdog.watchdog_test/045-TestWatchdogCRUD_REST;test_remove_watchdog/TestWatchdogCRUD_REST_test_remove_watchdog/ the bug occur in 22:04
can't see anything suspicious in the engine.log, it seems the delete of the watchdog works ok but for some reason the test fails when reading the response
This happens because the client is sending a request without including the "Accept" content header. In this situation the application server doesn't know how to convert the result to something that the client will understand, resulting in this error message: Could not find MessageBodyWriter for response object of type: org.ovirt.engine.api.model.Action of media type: application/octet-stream The best way to solve this problem is to modify the client so that it explicitly sends the "Accept" header: DELETE /vms/{vm:id}/wathdogs/{watchdog:id} Accept: application/xml It is also possible to modify the "BackendWatchdogResource" interface so that it explicitly includes the @Produces annotation with the supported media types. This will make the server consider those media types. For sake of backwards compatibility we will do that.
verified on 3.6.0-10
oVirt 3.6.0 has been released on November 4th, 2015 and should fix this issue. If problems still persist, please open a new BZ and reference this one.