Bug 1222659

Summary:	RHOS: Fleecing an image throws following error in evm.log file
Product:	Red Hat CloudForms Management Engine	Reporter:	Ramesh A <rananda>
Component:	SmartState Analysis	Assignee:	Hui Song <hsong>
Status:	CLOSED ERRATA	QA Contact:	Ramesh A <rananda>
Severity:	medium	Docs Contact:
Priority:	high
Version:	5.4.0	CC:	cpelland, jhardy, jprause, mfeifer, ncatling, obarenbo, roliveri
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.4.4
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.4.4.1	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-12-16 13:19:24 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:

Description Ramesh A 2015-05-18 18:34:22 UTC

Description of problem:
Fleecing an image throws following error in evm.log file stating "[----] E, [2015-05-18T14:26:45.160679 #3550:be5e9c] ERROR -- : Q-task_id([2e1b8a80-fd8b-11e4-8c20-fa163e8c5175]) TemplateOpenstack#scan_via_miq_vm ScanMetadata error status:[8]:  message:[Could not extract "["vmevents"]" from VM]"


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

How reproducible:
very

Steps to Reproduce:
1. Install a fresh appliance
2. Add vddk kit(for vsphere) or lun(for rhevm) based on where the appliance is deployed.  Reboot if necessary.
3. Manage a RHOS provider
4. Create a policy to use default analysis profile and associate it to smart state analysis start event
5. Assign this policy to an Image and Perform smart scan on it

Actual results:
Throws error message in evm.log stating :
"[----] E, [2015-05-18T14:26:45.160679 #3550:be5e9c] ERROR -- : Q-task_id([2e1b8a80-fd8b-11e4-8c20-fa163e8c5175]) TemplateOpenstack#scan_via_miq_vm ScanMetadata error status:[8]:  message:[Could not extract "["vmevents"]" from VM]"


Expected results:
Should not throw error message

Additional info:

Comment 2 Dave Johnson 2015-05-20 03:22:31 UTC

This is something to do with the differences between the hidden fallback scan profile versus copying the sample profile and naming it 'default' (which is usually what we do to start collecting file data).  

The sample profile (which we copy) is configured for vmevents but even when I remove the three default vmevent entries, I still get the error, or so it seemed.  When I created a default scan profile from 'new' though and only configured it for categories and /etc/*.conf , I did not received the error (although I didn;t receive file data either which will be a new BZ with the next build once confirmed)

Comment 3 Rich Oliveri 2015-10-14 18:40:26 UTC

This problem only exists in 5.4. The current upstream code that fixes this doesn't apply to the 5.4 code base. I'll change the target release to 5.4.z so we can use this ticked for the applicable downstream fix.

This fix is simple, the extract method of MiqVm should not raise an error when the returned XML is nil.

Comment 6 Hui Song 2015-10-20 13:44:28 UTC

Thank you, Rich. Now I changed it back.

Comment 8 Ramesh A 2015-12-09 12:17:24 UTC

Good to go.  Verified and working fine in 5.4.4.2.20151130143928_89a28ce

Comment 10 errata-xmlrpc 2015-12-16 13:19:24 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-2620.html