Bug 1129781

Summary: 500 internal error when adding watchdog to VM via CLI/REST
Product: [Retired] oVirt Reporter: Lukas Svaty <lsvaty>
Component: ovirt-engine-apiAssignee: Juan Hernández <juan.hernandez>
Status: CLOSED CURRENTRELEASE QA Contact: Lukas Svaty <lsvaty>
Severity: urgent Docs Contact:
Priority: medium    
Version: 3.5CC: bugs, ecohen, gklein, iheim, rbalakri, s.kieske, yeylon
Target Milestone: ---Keywords: TestBlocker, Triaged
Target Release: 3.5.0   
Hardware: All   
OS: All   
Whiteboard: sla
Fixed In Version: ovirt-3.5.0_rc2 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-10-17 12:33:35 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: SLA RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Lukas Svaty 2014-08-13 15:53:45 UTC 
Description of problem:
Adding watchdog with model and action fails on 500 internal error via ovirt-shell or REST

Version-Release number of selected component (if applicable):
ovirt-rc1

How reproducible:
100%

Steps to Reproduce:
1. curl -X POST -H "Accept: application/xml" -H "Content-Type: application/xml" -u admin@internal:$pwd --cacert ca.crt -d "<watchdog><model>i6300esb</model><action>reset</action></watchdog>" https://$url:443/api/vms/$vmid/watchdogs
<?xml version="1.0" encoding="UTF-8" standalone="yes"?><fault><reason>Operation Failed</reason></fault>[~] $ ^C

2. ovirt-shell ~ add watchdog --vm-identifier dd35488d-f247-461f-b45c-f6b7b004e270 --action reset --model i6300esb

  ==================================== ERROR =================================
  status: 500
  reason: Internal Server Error
  detail:
  ============================================================================


Actual results:


Expected results:


Additional info:
Comment 1 Lukas Svaty 2014-09-16 09:57:54 UTC 
verified in vt3.1
Comment 2 Sandro Bonazzola 2014-10-17 12:33:35 UTC 
oVirt 3.5 has been released and should include the fix for this issue.