Bug 989403
Summary: | [rhevm] - backend - Cannot create new VMs due to error on engine (MAC_POOL_NOT_INITIALIZED [General command validation failure]) | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Enterprise Virtualization Manager | Reporter: | David Botzer <dbotzer> | ||||
Component: | ovirt-engine | Assignee: | Nobody's working on this, feel free to take it <nobody> | ||||
Status: | CLOSED DUPLICATE | QA Contact: | |||||
Severity: | high | Docs Contact: | |||||
Priority: | high | ||||||
Version: | 3.3.0 | CC: | acathrow, iheim, lpeer, pstehlik, Rhev-m-bugs, yeylon | ||||
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: | 2013-08-22 09:37:44 UTC | Type: | Bug | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | Network | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
*** This bug has been marked as a duplicate of bug 987825 *** |
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: