Bug 989403 - [rhevm] - backend - Cannot create new VMs due to error on engine (MAC_POOL_NOT_INITIALIZED [General command validation failure])
Summary: [rhevm] - backend - Cannot create new VMs due to error on engine (MAC_POOL_NO...
Keywords:
Status: CLOSED DUPLICATE of bug 987825
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.3.0
Hardware: x86_64
OS: Linux
high
high
Target Milestone: ---
: ---
Assignee: Nobody's working on this, feel free to take it
QA Contact:
URL:
Whiteboard: network
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-29 08:31 UTC by David Botzer
Modified: 2016-02-10 19:49 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-08-22 09:37:44 UTC
oVirt Team: Network
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
error in engine (323.51 KB, application/x-gzip)
2013-07-29 08:31 UTC, David Botzer
no flags Details

Description David Botzer 2013-07-29 08:31:09 UTC
Created attachment 779679 [details]
error in engine

Description of problem:
[rhevm] - backend - Cannot create new VMs due to error on engine (MAC_POOL_NOT_INITIALIZED [General command validation failure])

Version-Release number of selected component (if applicable):
3.3/is6

How reproducible:
always

Steps to Reproduce:
1.Install rhevm+dwh+reports
2.Create new vm with rhevm-sdk (should fail)
3.Create new vm via webadmin

my MacPoolRange is
00:1A:4A:23:A1:00-00:1A:4A:23:A1:FF - so i have enough Macs

Actual results:
Webadmin error message :

Error while executing action:
aaaaa:
    General command validation failure. 
----
- engine.log shows
MAC_POOL_NOT_INITIALIZED (Failed with VDSM error MAC_POOL_NOT_INITIALIZED a
nd code 5011) 

Expected results:
Should aalow creating new VMs
Should display correct message corresponding to the correct error

Additional info:

Comment 1 Itamar Heim 2013-08-22 09:37:44 UTC

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


Note You need to log in before you can comment on or make changes to this bug.