Description of problem: Unable to complete a smart state anaylsis on a Windows 2016 Datacenter VM hosted on Azure Azure Region - South Central US VM Disk is not encrypted on Azure and storage account type is Standard_LRS Attached is a screen shot of the disk layout inside of the vm. [----] I, [2017-11-28T11:04:10.559675 #13089:c7f13c] INFO -- : Q-task_id([job_dispatcher]) MIQ(VmScan#process_data) starting... [----] I, [2017-11-28T11:04:10.574157 #13089:c7f13c] INFO -- : Q-task_id([job_dispatcher]) MIQ(VmScan#process_data) Document=summary [----] I, [2017-11-28T11:04:10.574823 #13089:c7f13c] INFO -- : Q-task_id([job_dispatcher]) MIQ(VmScan#process_data) sending :synchronize [----] I, [2017-11-28T11:04:10.629143 #13089:c7f13c] INFO -- : Q-task_id([job_dispatcher]) MIQ(VmScan#scanning) . [----] I, [2017-11-28T11:04:17.777000 #13089:c7f13c] INFO -- : Q-task_id([job_dispatcher]) MIQ(MiqQueue.put) Message id: [5241], id: [], Zone: [default], Role: [automate], Server: [], Ident: [generic], Target id: [], Instance id: [], Task id: [], Command: [MiqAeEngine.deliver], Timeout: [3600], Priority: [20], State: [ready], Deliver On: [], Data: [], Args: [{:object_type=>"ManageIQ::Providers::Azure::CloudManager::Vm", :object_id=>2, :attrs=>{:event _type=>"vm_scan_abort", "VmOrTemplate::vm"=>2, :vm_id=>2, :host=>nil, "MiqEvent::miq_event"=>1507, :miq_event_id=>1507, "EventStream::event_stream"=>1507, :event_stream_id=>1507}, :instance_name=>"Event", :user_id=>1, :miq_group _id=>2, :tenant_id=>2, :automate_message=>nil}] [----] E, [2017-11-28T11:04:17.777188 #13089:c7f13c] ERROR -- : Q-task_id([job_dispatcher]) MIQ(VmScan#process_abort) job aborting, Unable to mount filesystem. Reason:[Could not determine root drive letter.] [----] I, [2017-11-28T11:04:17.807131 #13089:c7f13c] INFO -- : Q-task_id([job_dispatcher]) MIQ(VmScan#process_finished) job finished, Unable to mount filesystem. Reason:[Could not determine root drive letter.] [----] I, [2017-11-28T11:04:17.815166 #13089:c7f13c] INFO -- : Q-task_id([job_dispatcher]) MIQ(VmScan#dispatch_finish) Dispatch Status is 'finished' Version-Release number of selected component (if applicable): 5.9.0.11.20171127204214_e316988 How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: This was a default deployment of a windows vm created by Azure.
Pending the response to the needinfo? above, PR https://github.com/ManageIQ/manageiq-smartstate/pull/47 fixes this issue.
New commit detected on ManageIQ/manageiq-smartstate/master: https://github.com/ManageIQ/manageiq-smartstate/commit/a155eccb66d26f5cab087e7b315e0f1c02a40b0c commit a155eccb66d26f5cab087e7b315e0f1c02a40b0c Author: Jerry Keselman <jerryk> AuthorDate: Wed Dec 13 14:29:21 2017 -0500 Commit: Jerry Keselman <jerryk> CommitDate: Wed Dec 13 14:37:14 2017 -0500 Assume C: Drive if Disk Sig Doesn't Match Serial Number If the Disk Signature of the root volume didn't match the serial number for one of the drives found in the BCD registry (or the boot.ini previously) the assumption was that we could not map the root to a mount point. However - the logic in the code already made the assumption that if there were no drives found in the registry that the C drive should be used. This change also makes that assumption in the case that the disk signature doesn't match a registry entry. Fixes https://bugzilla.redhat.com/show_bug.cgi?id=1518347 lib/fs/modules/WinMount.rb | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-)
The fix is included in manageiq-smartstate gem v0.2.6
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days