Bug 1731853 - [v2v] Harmless "start is not permitted at state running" errors in the evm.log
Summary: [v2v] Harmless "start is not permitted at state running" errors in the evm.log
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: V2V
Version: 5.10.7
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: GA
: 5.10.z
Assignee: Fabien Dupont
QA Contact: Sudhir Mallamprabhakara
Red Hat CloudForms Documentation
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-07-22 08:31 UTC by Ilanit Stein
Modified: 2020-05-13 17:15 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-05-13 17:15:28 UTC
Category: Bug
Cloudforms Team: V2V
Target Upstream Version:

Attachments (Terms of Use)
evm.log (10.03 MB, application/gzip)
2019-07-22 08:38 UTC, Ilanit Stein 		no flags Details
automation.log (5.00 MB, application/gzip)
2019-07-22 08:38 UTC, Ilanit Stein 		no flags Details
Add an attachment (proposed patch, testcase, etc.)

Description Ilanit Stein 2019-07-22 08:31:08 UTC 
Description of problem:
In 2 v2v migration of 20 VMs/100GB disk, such error are displayed in evm.log:

[----] E, [2019-07-21T12:24:25.696326 #4580:892f60] ERROR -- : Q-task_id([job_dispatcher]) MIQ(MiqQueue#deliver) Message id: [118032], Error: [start is not permitted at state running]
[----] E, [2019-07-21T12:24:25.696555 #4580:892f60] ERROR -- : Q-task_id([job_dispatcher]) [RuntimeError]: start is not permitted at state running  Method:[block (2 levels) in <class:LogProxy>]
[----] E, [2019-07-21T12:24:25.696754 #4580:892f60] ERROR -- : Q-task_id([job_dispatcher]) /var/www/miq/vmdb/app/models/job/state_machine.rb:36:in `signal'

In the first migration run - all VMs were migrated successfully, 
and these messages appeared at the beginning of the migration.

In the second migration run, migration was cancelled for 2 VMs,
and the other 18 VMs migration started, shortly after the second migration round started, those errors started.

Version-Release number of selected component (if applicable):
CFME-5.10.7.1/RHV-4.3.5

Expected:
Such errors messages should not appear. At least not as ERRORs.  

Additional info:
Though it seem these errors are not failing the VMs migration, 
they should not appear as ERRORs in the evm.log.
Maybe turn them into WARNINGs or DEBUG, or find another solution.
Comment 2 Ilanit Stein 2019-07-22 08:38:29 UTC 
Created attachment 1592547 [details]
evm.log

First migration run. Errors appear @ July 21 2019 8:03
Second migration run. Errors appear @ July 21 2019 12:24
Comment 3 Ilanit Stein 2019-07-22 08:38:59 UTC 
Created attachment 1592548 [details]
automation.log
Note You need to log in before you can comment on or make changes to this bug.