Bug 1448527

Summary: Report no ReFS FileSystem Support
Product: Red Hat CloudForms Management Engine Reporter: Satoe Imaishi <simaishi>
Component: SmartState AnalysisAssignee: Rich Oliveri <roliveri>
Status: CLOSED ERRATA QA Contact: Jeff Teehan <jteehan>
Severity: high Docs Contact:
Priority: high    
Version: 5.8.0CC: cpelland, jhardy, obarenbo, roliveri, simaishi
Target Milestone: GA   
Target Release: 5.8.0   
Hardware: Unspecified   
OS: Windows   
Whiteboard: provider:ssa:exception
Fixed In Version: 5.8.0.12 Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: 1445541 Environment:
Last Closed: 2017-05-31 15:09:38 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: Bug
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: CFME Core Target Upstream Version:
Embargoed:
Bug Depends On: 1445541    
Bug Blocks:    

Comment 2 Satyajit Bulage 2017-05-09 06:16:11 UTC 
Hello, 

Please, can you add verification steps..?

Thanks,
Satyajit Bulage.
Comment 3 Rich Oliveri 2017-05-09 15:20:57 UTC 
Attempt to perform SSA on a windows VM that has a ReFS root filesystem.
The SSA attempt should fail, but the error message should indicate that ReFS is currently not supported.
Comment 4 Jeff Teehan 2017-05-26 18:26:52 UTC 
I got it figured out.  You need an underlying ReFS storage system and you only need to add a second data disk to windows.

Here is a successful SSA on the VM with no ReFS disk.

05/26/17 16:12:45 UTC	05/26/17 16:08:30 UTC	05/26/17 16:08:26 UTC	finished	Process completed successfully	Scan from Vm ReFS16on16a	admin	EVM	Synchronization complete

Here is the error with the ReFS disk attached:

05/26/17 18:13:36 UTC	05/26/17 18:10:56 UTC	05/26/17 18:10:46 UTC	finished	Unable to mount filesystem. Reason:[ReFS is Not Supported]	Scan from Vm ReFS16on16a	admin	EVM	Scanning completed.

Moving to verified using 5.8.0.17
Comment 6 errata-xmlrpc 2017-05-31 15:09:38 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://access.redhat.com/errata/RHSA-2017:1367