Bug 1392587

Summary: SmartState analysis failed after upgrade to 5.6.2.2
Product: Red Hat CloudForms Management Engine Reporter: Saif Ali <saali>
Component: SmartState AnalysisAssignee: Hui Song <hsong>
Status: CLOSED WORKSFORME QA Contact: Dave Johnson <dajohnso>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.6.0CC: cpelland, hsong, jfrey, jhardy, jocarter, myoder, obarenbo, roliveri, saali, sbulage
Target Milestone: GAKeywords: Reopened
Target Release: 5.6.4   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: smartstate
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-20 21:34:25 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 logs none

Description Saif Ali 2016-11-07 20:09:16 UTC
Created attachment 1218234 [details]
evm logs

Description of problem:
After upgrade to 5.6.2.2 unable to run SmartState analysis  on VMs 
[----] E, [2016-11-07T15:11:55.747357 #3061:80f994] ERROR -- : Q-task_id([a3ddb558-a515-11e6-9f3d-005056a5f3fa]) MIQ(VmScan#process_abort) job aborting, No eligible proxies for VM :[[DS_LUN02] rhel_CA_S_0002/rhel_CA_S_0002.vmx] - [No active SmartProxies found to analyze this VM], aborting job [a3ddb558-a515-11e6-9f3d-005056a5f3fa].
We verified the server roles running also 
grep :role: log/last_startup.txt 

Version-Release number of selected component (if applicable):
CFME 5.6.2.2
vCenter version is: 5.5.0 (build 2646482)

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Dave Johnson 2016-11-11 06:23:18 UTC
Satyajit, can you try to reproduce this please next week during the 5.6.3 test day.  Ping jkrocil or lcouz if you need help upgrading.  Once you confirm or deny, then please update with the scl repo and see if that is the root cause.

Comment 3 Satyajit Bulage 2016-11-11 07:11:27 UTC
Dave,

Yes, I will try to reproduce this issue next week during 5.6.3 test day and update this bz with proper observations.

Thanks,
Satyajit Bulage.

Comment 16 Hui Song 2016-12-16 14:39:41 UTC
Feel free to open it if this issue happens again.

Comment 22 Hui Song 2017-01-20 21:34:25 UTC
Issue closed.