Bug 1376172

Summary:	BAT Handling in Checkpoint Disks Issues
Product:	Red Hat CloudForms Management Engine	Reporter:	Satoe Imaishi <simaishi>
Component:	SmartState Analysis	Assignee:	Jerry Keselman <jkeselma>
Status:	CLOSED ERRATA	QA Contact:	Jeff Teehan <jteehan>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	5.6.0	CC:	jhardy, jkeselma, obarenbo, simaishi
Target Milestone:	GA	Keywords:	ZStream
Target Release:	5.6.2
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	5.6.2.0	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:	1375229	Environment:
Last Closed:	2016-10-04 14:34:14 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	Unknown	Target Upstream Version:
Embargoed:
Bug Depends On:	1375229
Bug Blocks:

Comment 3 Jerry Keselman 2016-09-27 11:49:46 UTC

This issue was not related to Azure SSA - it was caused by SCVMM / Hyper-V checkpoint handling.  Checkpoint disks are created when a snapshot is created.  So a good test would be to take a snapshot of the VM and try to run SSA on it.

Comment 4 Jeff Teehan 2016-10-03 17:22:39 UTC

Create a vm with a snapshot disk.  You can see it picked the avhdx disk to grab the data.

Parent Host Platform	HyperV
Platform Tools	OS shutdown: true, Time synchronization: true, Data exchange: true, Heartbeat: true, Backup: true
Operating System	 Windows 7 Professional
Devices	 4
CPU Affinity	
Snapshots	 1
Configuration
Applications	 2
Win32 Services	 153
Kernel Drivers	 249
File System Drivers	 25
Files	 7
Registry Entries	 24

[----] I, [2016-10-03T13:08:12.770695 #3214:ac3988]  INFO -- : MIQ(MiqAlert.evaluate_alerts) [vm_scan_complete] Target: ManageIQ::Providers::Microsoft::InfraManager::Vm Name: [Local33SSATest], Id: [922000000000055]


Tested using 5.6.2.1 on 10.16.7.89.  Moving to verified.

Comment 6 errata-xmlrpc 2016-10-04 14:34:14 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-2016-1996.html