Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 848391

Summary: Add non-existing Network to Cluster - empty error message
Product: Red Hat Enterprise Virtualization Manager Reporter: lpeer <lpeer>
Component: ovirt-engineAssignee: Mike Kolesnik <mkolesni>
Status: CLOSED CURRENTRELEASE QA Contact: GenadiC <gcheresh>
Severity: medium Docs Contact:
Priority: low    
Version: 3.1.0CC: acathrow, dyasny, hateya, iheim, lpeer, mgoldboi, oliel, Rhev-m-bugs, sgrinber, yeylon, ykaul
Target Milestone: ---Keywords: EasyFix
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: network
Fixed In Version: si16 Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: 743830 Environment:
Last Closed: 2012-12-04 20:00:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Network RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 743830    
Bug Blocks:    

Description lpeer 2012-08-15 13:26:19 UTC 
+++ This bug was initially created as a clone of Bug #743830 +++

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 lpeer 2012-08-20 10:31:46 UTC 
http://gerrit.ovirt.org/7333
Comment 4 GenadiC 2012-09-02 14:22:00 UTC 
Verified in SI16