Created attachment 1361264 [details] Snippet of evm.log file showing the issue. Description of problem: On certain Azure Blob Disk Windows Instances, the following error is written to the log during Smartstate Analysis: ERROR -- : MIQ(NTFS::IndexRecordHeader.initialize) Invalid Index Record Header because: <NTFS Fixup Error: fixup signature:<22> does not match signature[8]=<18>. Subsequently the scans continue, but the error message MIQ(ManageIQ::Providers::Azure::CloudManager::Vm#scan_via_miq_vm) Error: No XML returned for category [software] is written to the log. The scans give the impression of succeeding, but the applications at the very least are not processed correctly. Version-Release number of selected component (if applicable): How reproducible: Occasionally Steps to Reproduce: 1. Run smartstate against certain Azure Windows Blob Disk Instances. See the attached log files for examples. 2. 3. Actual results: Scan is not entirely successful. Expected results: Scan is successful. Additional info: Two log snippets will be attached.
Created attachment 1361266 [details] Another log snippet showing the error. Another log snippet showing the error on a different Instance.
This issue is based on a log attached to the BZ https://bugzilla.redhat.com/show_bug.cgi?id=1508154 which shows several issues which now each have their own BZs.