Bug 743830

Summary: Add non-existing Network to Cluster - empty error message
Product: [Retired] oVirt Reporter: Ori Liel <oliel>
Component: ovirt-engine-coreAssignee: Mike Kolesnik <mkolesni>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: low Docs Contact:
Priority: low    
Version: unspecifiedCC: acathrow, dyasny, iheim, lpeer, mgoldboi, mkolesni, Rhev-m-bugs, yeylon, ykaul
Target Milestone: ---Keywords: EasyFix
Target Release: 3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 848391 (view as bug list) Environment:
Last Closed: 2013-02-15 06:47:45 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On:    
Bug Blocks: 848391    

Description Ori Liel 2011-10-06 08:28:41 UTC
Steps to reproduce: 

1) Add network to cluster, with a network-id that doesn't exist in rhevm database, for example: 

  <network id="2b8efd92-1779-40db-87a4-043f27dd3bc0">
    <name>green</name>
  </network>

2) Failure at database level (naturally).

3) VdcReturnValueBase object, which is returned, has emtpy executeFailedMessages[] array (the error can be seen only in 'fault' field which is internal).


Expected Results: 

VdcReturnValueBase-->executeFailedMessages[] should contain a description of the failure.

Comment 1 Mike Kolesnik 2012-08-20 09:13:40 UTC
http://gerrit.ovirt.org/7333

Comment 3 Itamar Heim 2013-01-16 16:10:14 UTC
3.2 beta built, moving to ON_QA status to allow testing