Bug 1388982

Summary: Tasks screen does not reflect a failed smart state scan.
Product: Red Hat CloudForms Management Engine Reporter: Josh Carter <jocarter>
Component: SmartState AnalysisAssignee: Hui Song <hsong>
Status: CLOSED DUPLICATE QA Contact: Ilanit Stein <istein>
Severity: high Docs Contact:
Priority: unspecified    
Version: 5.7.0CC: jhardy, obarenbo, roliveri
Target Milestone: GA   
Target Release: cfme-future   
Hardware: All   
OS: All   
Whiteboard: rhev:smartscan
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-07 15:58:09 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: RHEVM Target Upstream Version:

Description Josh Carter 2016-10-26 15:35:27 UTC 
Description of problem:

When a rhev smart state fails the tasks screen does not display the failed smart state scan. The status will still reflect that its "running" 

[----] I, [2016-10-26T03:21:25.069576 #4268:c23148]  INFO -- : MIQ(VmScan#call_snapshot_create) Enter
[----] I, [2016-10-26T03:21:25.080370 #4268:c23148]  INFO -- : EVM SmartState Analysis Initiated for VM [cfme001]
[----] W, [2016-10-26T03:21:25.080760 #4268:c23148]  WARN -- : User event logging is not available on [ManageIQ::Providers::Redhat::InfraManager] Name:[skynet-rhev]
[----] I, [2016-10-26T03:21:25.106239 #4268:c23148]  INFO -- : MIQ(VmScan#call_scan) Enter
[----] I, [2016-10-26T03:21:25.464324 #4268:c23148]  INFO -- : MIQ(ManageIQ::Providers::Redhat::InfraManager::Vm#scan_metadata) category=[["vmconfig", "accounts", "software", "services", "system"]] [Array]
[----] E, [2016-10-26T03:21:25.523048 #4268:c23148] ERROR -- : [NoMethodError]: undefined method `key?' for nil:NilClass  Method:[rescue in scan_metadata]
[----] E, [2016-10-26T03:21:25.523363 #4268:c23148] ERROR -- : /opt/rh/rh-ruby23/root/usr/share/ruby/ostruct.rb:176:in `respond_to_missing?'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:381:in `respond_to?'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:381:in `init_with'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:374:in `revive'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:208:in `visit_Psych_Nodes_Mapping'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/visitor.rb:16:in `visit'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/visitor.rb:6:in `accept'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:32:in `accept'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:330:in `block in register_empty'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:330:in `each'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:330:in `register_empty'
/opt/rh/rh-ruby23/root/usr/share/gems/gems/psych-2.0.17/lib/psych/visitors/to_ruby.rb:141:in `visit_Psych_Nodes_Sequence'

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

 Version 5.7.0.7-beta1.20161025153249_9376fbd 

How reproducible:
very

Steps to Reproduce:
1. 
2.
3.

Actual results:


Expected results:


Additional info:
Comment 2 Rich Oliveri 2016-10-28 15:31:11 UTC 
It appears this may be the same problem as:

https://bugzilla.redhat.com/show_bug.cgi?id=1378447
and
https://bugzilla.redhat.com/show_bug.cgi?id=1389026

so the problem probably a more general problem. I'll assign it to someone on my team to make the determination.
Comment 3 Hui Song 2016-11-07 15:58:09 UTC 
This issue is caused by a ruby bug: https://bugs.ruby-lang.org/issues/11884. Ruby version of 2.3.1 will solve the problem.

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