Bug 1399279

Summary: new vmpool creation failed
Product: [oVirt] ovirt-engine Reporter: Eldad Marciano <emarcian>
Component: Backend.CoreAssignee: Tal Nisan <tnisan>
Status: CLOSED DUPLICATE QA Contact: meital avital <mavital>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.0.6.1CC: bugs, michal.skrivanek, tnisan
Target Milestone: ovirt-4.0.6Flags: tnisan: ovirt-4.0.z?
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-29 06:49:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Storage RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
engine log none

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 ***