Bug 1339637 - Smart State Analysis timed out scans are not displayed as "timed out" in CFME
Summary: Smart State Analysis timed out scans are not displayed as "timed out" in CFME
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: GA
: 5.7.0
Assignee: Erez Freiberger
QA Contact: Einat Pacifici
URL:
Whiteboard: container:smartstate
Depends On:
Blocks: 1341667
TreeView+ depends on / blocked
 
Reported: 2016-05-25 13:49 UTC by Tony
Modified: 2018-04-17 07:58 UTC (History)
8 users (show)

Fixed In Version: 5.7.0.0
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 1341667 (view as bug list)
Environment:
Last Closed: 2017-01-11 19:54:51 UTC
Category: ---
Cloudforms Team: Container Management
Target Upstream Version:
Embargoed:
epacific: automate_bug+


Attachments (Terms of Use)
CFME My Tasks (165.97 KB, image/png)
2016-05-25 14:13 UTC, Tony
no flags Details

Description Tony 2016-05-25 13:49:37 UTC
Description of problem:


When performing a Smart State Analysis scheduled scans with the provider attached to OpenSCAP policy, some images time out (with the actual 10 min timeout instead of a 3 min timeout). Those images are displayed in CFME as "scanning"



Steps to Reproduce:
1. Attach a provider to OpenSCAP policy
2. Schedule a scan
3. After 10-15 minutes check the results of the scan in evm.log (appear to be timed out) and in CFME (appear as "scanning")

Comment 2 Tony 2016-05-25 14:05:13 UTC
Log file will be attached shortly

Comment 3 Tony 2016-05-25 14:13:07 UTC
The evm.log can be viewed at

https://drive.google.com/open?id=0BwFOPs7diTYdc21xSFN1V0gtQWM

Comment 4 Tony 2016-05-25 14:13:45 UTC
Created attachment 1161456 [details]
CFME My Tasks

Comment 5 Greg Blomquist 2016-05-26 14:19:18 UTC
Federico, wasn't sure if this was a general SSA issue or specific to containers.  I've asked Dajo to retest scan timeouts on Compute Images to see if he can get the same problem.

Comment 6 Mooli Tayer 2016-05-29 11:07:16 UTC
Erez my 5 cents on this issue:

There are types of timeouts I've seen in scanning/job.rb

1. Organic timeouts
e.g the job timesout because OpenShift could not download an image in time

2. An exception was thrown when the job was running, and then some 
other component times out the job (that can happen from model/job.rb or from miq_queue as you explained to me today) 

we will have a stack trace in evm.log with the original exception in that case

Comment 7 Erez Freiberger 2016-06-01 08:57:46 UTC
A proposed fix: https://github.com/ManageIQ/manageiq/pull/9040/files

Comment 9 Tony 2016-09-28 10:34:39 UTC
Verified on CFME 5.7.0.1


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