Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 1367024 - VM pool creation task can't finish
Summary: VM pool creation task can't finish
Keywords:
Status: CLOSED DUPLICATE of bug 1310426
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 3.6.7
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Liron Aravot
QA Contact: meital avital
URL:
Whiteboard:
Depends On: 1310426
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-08-15 09:45 UTC by Olimp Bockowski
Modified: 2017-03-19 16:15 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-18 12:42:24 UTC
oVirt Team: Storage


Attachments (Terms of Use)
engine.log (deleted)
2016-08-15 13:23 UTC, Olimp Bockowski
no flags Details

Description Olimp Bockowski 2016-08-15 09:45:46 UTC
Description of problem:
There is problem with task status when someone wants to create VM Pool.
Although VM Pool with VMs are created, task is still reported as pending at "Executing" / "Finalizing" stage. 
In engine DB in job table creating VM Pool (action_type AddVmPoolWithVms) is reported as STARTED. 

Version-Release number of selected component (if applicable):
RHEV 3.6.7 

How reproducible:
100% - every time we try to create VM Pool

Steps to Reproduce:
1. create VM Pool: VM Pool tab / click New / pick up template and click ok
2. VM Pool is created, VMs are created
3. task is still pending, in engine DB status is STARTED

Actual results:
task are "finalizing" 

Expected results:
after VM pool and VM successful creation task should be removed.

Comment 1 Tomas Jelinek 2016-08-15 12:36:09 UTC
could you please provide the engine.log for the relevant timeframe?

Comment 2 Olimp Bockowski 2016-08-15 13:23:24 UTC
Created attachment 1190913 [details]
engine.log

correlation id in engine DB: 78e51ff7

Comment 4 Allon Mureinik 2016-08-16 08:49:33 UTC
Liron - didn't you recently handle a similar issue?


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