Bug 1392587 - SmartState analysis failed after upgrade to 5.6.2.2
Summary: SmartState analysis failed after upgrade to 5.6.2.2
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: GA
: 5.6.4
Assignee: Hui Song
QA Contact: Dave Johnson
URL:
Whiteboard: smartstate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-07 20:09 UTC by Saif Ali
Modified: 2020-02-14 18:06 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-01-20 21:34:25 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:

Attachments (Terms of Use)
evm logs (8.72 MB, application/x-xz)
2016-11-07 20:09 UTC, Saif Ali 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

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.
Note You need to log in before you can comment on or make changes to this bug.