Bug 1399279 - new vmpool creation failed
Summary: new vmpool creation failed
Keywords:
Status: CLOSED DUPLICATE of bug 1397866
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: Backend.Core
Version: 4.0.6.1
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ovirt-4.0.6
: ---
Assignee: Tal Nisan
QA Contact: meital avital
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-28 16:46 UTC by Eldad Marciano
Modified: 2016-11-29 13:20 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-29 06:49:12 UTC
oVirt Team: Storage
Embargoed:
tnisan: ovirt-4.0.z?

Attachments (Terms of Use)
engine log (7.00 MB, application/zip)
2016-11-28 16:46 UTC, Eldad Marciano 		no flags Details
View All

Description Eldad Marciano 2016-11-28 16:46:07 UTC 
Created attachment 1225358 [details]
engine log

Description of problem:
vmpool creation failed due to:
2016-11-28 16:16:34,229 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (org.ovirt.thread.pool-6-thread-35) [5af9eb5a] Correlation ID: 1de1e72f, Job ID: 667d7ba9-cb84-440b-bea8-81d06fdfbbcb, Call Stack: null, Custom Event ID: -1, Message: Failed to create VM Pool momz_??? (User: admin@internal-authz).
2016-11-28 16:16:36,301 ERROR [org.ovirt.engine.core.bll.AddVmPoolWithVmsCommand] (DefaultQuartzScheduler15) [5af9eb5a] Ending command 'org.ovirt.engine.core.bll.AddVmPoolWithVmsCommand' with failure.
2016-11-28 16:16:41,931 ERROR [org.ovirt.engine.core.vdsbroker.vdsbroker.VdsBrokerObjectsBuilder] (DefaultQuartzScheduler18) [36090fc7] null architecture type, replacing with x86_64, %s



Version-Release number of selected component (if applicable):
4.0.6-1

How reproducible:
100%

Steps to Reproduce:
1. login
2. create a vm pool with any template
3.

Actual results:
vmpool creation failed


Expected results:
vmpool creation pass

Additional info:
Comment 1 Michal Skrivanek 2016-11-29 06:49:12 UTC 

*** This bug has been marked as a duplicate of bug 1397866 ***
Note You need to log in before you can comment on or make changes to this bug.