Bug 1455469 - Live storage migration tasks polling should start right away
Summary: Live storage migration tasks polling should start right away
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: BLL.Storage
Version: 4.1.0.2
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.1.3
: 4.1.3
Assignee: Liron Aravot
QA Contact: Eyal Shenitzky
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-25 09:16 UTC by Liron Aravot
Modified: 2017-07-06 13:23 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-06 13:23:17 UTC
oVirt Team: Storage
Embargoed:
rule-engine: ovirt-4.1+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 77298 0 ovirt-engine-4.1 MERGED core: CreateImagePlaceholder/SyncImageGroupData - setEntityInfo() 2017-05-25 12:51:35 UTC

Description Liron Aravot 2017-05-25 09:16:59 UTC
Description of problem:
When the live storage migration (CreateImagePlaceholder/SyncImageGroupData phases) tasks are created, there is pre-polling period before the AsyncTaskManager starts to poll them.

How reproducible:
Always

Steps to Reproduce:
1. Have a dc with 2 active storage domain
2. Create a vm with a disk
3. Start the vm
4. Move the disk when the vm is running

Actual results:
The task will enter pre-polling period of 60000 milli seconds before the engine will start to poll it.. 

Expected results:
The engine should start poll the task right away.

Additional info:
Example to a log when the task is in the pre polling phase -
2017-05-25 09:30:28,003+03 INFO  [org.ovirt.engine.core.bll.tasks.AsyncTaskManager] (DefaultQuartzScheduler10) [768eb9a1-f1b7-4681-880f-f1c154033d1c] Adding task '37c25602-3
59f-4d01-8256-cc85ffadb70b' (Parent Command 'SyncImageGroupData', Parameters Type 'org.ovirt.engine.core.common.asynctasks.AsyncTaskParameters'), polling hasn't started yet.
.
2017-05-25 09:30:28,023+03 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler10) [768eb9a1-f1b7-4681-880f-f1c154033d1c] BaseAsyncTask::startPolling
Task: Starting to poll task '37c25602-359f-4d01-8256-cc85ffadb70b'.
2017-05-09 09:30:30,162+03 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (DefaultQuartzScheduler6) [202134b8] Task id '37c25602-359f-4d01-8256-cc85ffadb70b' is in pre
-polling  period and should not be polled. Pre-polling period is 60000 millis.

Comment 1 rhev-integ 2017-05-28 14:46:10 UTC
INFO: Bug status wasn't changed from MODIFIED to ON_QA due to the following reason:

[Tag 'ovirt-engine-4.1.3' doesn't contain patch 'https://gerrit.ovirt.org/77298']
gitweb: https://gerrit.ovirt.org/gitweb?p=ovirt-engine.git;a=shortlog;h=refs/tags/ovirt-engine-4.1.3

For more info please contact: infra

Comment 2 Allon Mureinik 2017-06-01 12:43:16 UTC
This is included in the ovirt-engine-4.1.3.1 tag, moving to ON_QA

Comment 3 Eyal Shenitzky 2017-06-04 12:07:47 UTC
Liron, Can you pls write the log message that should appear in order to verify that the AsyncTaskManager starts to poll?

Comment 4 Allon Mureinik 2017-06-04 12:53:47 UTC
(In reply to Eyal Shenitzky from comment #3)
> Liron, Can you pls write the log message that should appear in order to
> verify that the AsyncTaskManager starts to poll?

You should see something like this:

2017-06-04 09:26:12,874+03 INFO  [org.ovirt.engine.core.bll.tasks.SPMAsyncTask] (org.ovirt.thread.pool-6-thread-12) [0948957d-018f-481b-b0db-5d45b8b31f02] BaseAsyncTask::startPollingTask: Starting to poll task '11dd5304-978b-4eaf-9b85-79e41ad0a263'

Comment 5 Eyal Shenitzky 2017-06-06 07:19:50 UTC
 Verified with the following code:
---------------------------------------
VDSM - 4.19.17-1.el7ev.x86_64
RHEVM - 4.1.3.1-0.1.el7

Steps to reproduce:
------------------------
1. Have a dc with 2 active storage domain
2. Create a vm with a disk
3. Start the vm
4. Move the disk when the vm is running

Moving to VERIFIED


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