Bug 1428758

Summary: SSA on Host does not finishes correctly.
Product: Red Hat CloudForms Management Engine Reporter: Satyajit Bulage <sbulage>
Component: ProvidersAssignee: Adam Grare <agrare>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: high    
Version: 5.8.0CC: gblomqui, istein, jfrey, jhardy, obarenbo
Target Milestone: GAKeywords: Regression
Target Release: cfme-future   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: smartstate:vmware
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-03-23 20:10:19 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:
Embargoed:
Attachments:
Description Flags
Screenshot showing actual results
none
evm.log for RHV provider testing none

Description Satyajit Bulage 2017-03-03 10:33:57 UTC
Created attachment 1259469 [details]
Screenshot showing actual results

Description of problem: After setting required environment for Host analysis Performed SmartState Analysis on vSphere's Host.


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


How reproducible:100%


Steps to Reproduce:
1.Add vSphere provider and set Host credentials
2.Perform SmartState Analysis on Host
3.

Actual results: Host analysis stuck at "Refreshing Log Information" message in tasks and never finishes.


Expected results: Host analysis should finish without any fail.


Additional info:

Comment 2 Ilanit Stein 2017-03-07 15:05:31 UTC
Created attachment 1260849 [details]
evm.log for RHV provider testing

Comment 4 Adam Grare 2017-03-23 20:10:19 UTC
I was able to reproduce this on 5.8.0.3 but not upstream/master.  This appears to have been fixed by https://github.com/ManageIQ/manageiq-gems-pending/pull/89 in BZ https://bugzilla.redhat.com/show_bug.cgi?id=1430770

Closing this issue as a duplicate.

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