Bug 842113

Summary: No pop up error message when configuring more NICs than allowed on VM
Product: Red Hat Enterprise Virtualization Manager Reporter: GenadiC <gcheresh>
Component: ovirt-engine-webadmin-portalAssignee: lpeer <lpeer>
Status: CLOSED DUPLICATE QA Contact: GenadiC <gcheresh>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 3.1.0CC: alkaplan, dyasny, ecohen, iheim, Rhev-m-bugs, sgrinber, ykaul
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: Network
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-07-30 11:20:36 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log with the problem attached none

Description GenadiC 2012-07-22 08:26:18 UTC 
Description of problem:
If you configure more NICs on the VM than allowed you are supposed to get a pop up error message and you do not.

How reproducible:
Always

Steps to Reproduce:
1. Create max amount of NICs on VM 
2. Try to add additional NIC
3.
  
Actual results:
No pop up error message is displayed in GUI, although the action fails

Expected results:
Pop up message should be displayed with appropriate error

Additional info:
I created 24 NICs on VM to reproduce the problem and got the following on engine log: CanDoAction of action AddVmInterface failed. Reasons:VAR__ACTION__ADD,VAR__TYPE__INTERFACE,NETWORK_INTERFACE_NAME_ALREADY_IN_USE
Comment 1 lpeer 2012-07-22 10:43:38 UTC 
Can you please attach backend logs?
Comment 2 GenadiC 2012-07-24 07:54:29 UTC 
Created attachment 599935 [details]
engine log with the problem attached
Comment 3 Alona Kaplan 2012-07-24 08:53:18 UTC 
works for me.
Comment 4 GenadiC 2012-07-26 09:59:15 UTC 
It happens randomly (at least 3 times in the last 2 days), will check if SI12 solved the problem
Comment 5 GenadiC 2012-07-29 09:46:34 UTC 
We see the same behaviour in SI12 as well, so the problem is not solved
Comment 6 Alona Kaplan 2012-07-30 11:20:36 UTC 

*** This bug has been marked as a duplicate of bug 842112 ***