Bug 1724487

Summary: [v2v] While VMs are migrated tens of ssh-agent errors appear in evm.log
Product: Red Hat CloudForms Management Engine Reporter: Ilanit Stein <istein>
Component: V2VAssignee: Daniel Berger <dberger>
Status: CLOSED CURRENTRELEASE QA Contact: Yadnyawalk Tale <ytale>
Severity: medium Docs Contact: Red Hat CloudForms Documentation <cloudforms-docs>
Priority: medium    
Version: unspecifiedCC: bthurber, dagur, fdupont, mshriver, simaishi
Target Milestone: GAKeywords: TestOnly, ZStream
Target Release: 5.11.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: v2v
Fixed In Version: 5.11.0.13 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 1725960 (view as bug list) Environment:
Last Closed: 2019-12-13 15:01:01 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: V2V Target Upstream Version:
Embargoed:
Bug Depends On: 1728295    
Bug Blocks: 1725960    
Attachments:
Description Flags
evm.log none

Description Ilanit Stein 2019-06-27 07:48:37 UTC 
Description of problem:
When migrating 20 VMs/100GB, tens of such error appear in evm.log:

[----] E, [2019-06-26T08:40:27.348504 #12387:38af54] ERROR -- net.ssh.authentication.agent[a9d5ae4]: Q-task_id([job_dispatcher]) could not connect to ssh-agent: Agent not configured

Those errors are NOT failing the VMs migration. 
but do spam the evm.log
 

Version-Release number of selected component (if applicable):
CFME-5.10.6.1/4.3.4.3-0.1.el7
Comment 2 Ilanit Stein 2019-06-27 07:49:28 UTC 
Created attachment 1585052 [details]
evm.log
Comment 3 Fabien Dupont 2019-06-27 08:19:18 UTC 
@Dan, this should be a quick fix in verify_credentials.
Comment 4 Daniel Berger 2019-06-27 12:54:26 UTC 
https://github.com/ManageIQ/manageiq/pull/18920
Comment 5 Daniel Gur 2019-07-01 09:30:19 UTC 
Maybe it can be fixed in 5.10.7 ?
Comment 8 Yadnyawalk Tale 2019-07-30 13:06:32 UTC 
Fixed, tested on 5.11.0.16.20190724210259_2b4aa51, did not found such errors when we ran SSH migrations.