Bug 1390581

Summary: SSA scans fails with "job timed out after xxx seconds...."
Product: Red Hat CloudForms Management Engine Reporter: Einat Pacifici <epacific>
Component: SmartState AnalysisAssignee: Hui Song <hsong>
Status: CLOSED DUPLICATE QA Contact: Einat Pacifici <epacific>
Severity: high Docs Contact:
Priority: high    
Version: 5.7.0CC: dajohnso, jhardy, obarenbo
Target Milestone: GA   
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: containers
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-07 15:01:16 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
evm.log attached for SSA none

Description Einat Pacifici 2016-11-01 12:56:27 UTC
Created attachment 1216108 [details]
evm.log attached for SSA

Description of problem:
When running Smart State Analysis scans on container images, no scans complete successfully. 
The error shown in the tasks list is: "job timed out after <xxx> seconds..."

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

How reproducible:
Always

Steps to Reproduce:
1.Add containers provider to CFME
2.Go to Compute --> Containers ---> Container Images
3.Select image
4. Select Configuration --> Perform Smart State Analysis
5. Wait up to 300 seconds (that's the timeout limit)

Actual results:
Scan entry is seen in Tasks list with error: "job timed out...."

Expected results:
Some scans should pass and complete successfully. 

Additional info:
evm.log attached.

Comment 2 Rich Oliveri 2016-11-03 14:26:20 UTC
Hui,

This may be related to the issues you're currently investigating.

Comment 3 Hui Song 2016-11-03 15:24:39 UTC
It's proved to be a ruby bug: https://bugs.ruby-lang.org/issues/11884. Will prepare a solution.

Comment 4 Hui Song 2016-11-07 15:01:16 UTC

*** This bug has been marked as a duplicate of bug 1378447 ***