Bug 1394370 - SmartState analysis Unable to mount filesystem
Summary: SmartState analysis Unable to mount filesystem
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis
Version: 5.6.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: GA
: cfme-future
Assignee: Rich Oliveri
QA Contact: Satyajit Bulage
URL:
Whiteboard: smartstate
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-11 19:56 UTC by Saif Ali
Modified: 2020-02-14 18:08 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-07-14 01:19:05 UTC
Category: ---
Cloudforms Team: ---
Target Upstream Version:


Attachments (Terms of Use)
appliance logs (5.65 MB, application/x-xz)
2016-11-11 19:56 UTC, Saif Ali
no flags Details

Description Saif Ali 2016-11-11 19:56:32 UTC
Created attachment 1219859 [details]
appliance logs

Description of problem:
SmartState is failing with ERROR -- : Unable to mount filesystem. The VM live on Cluster Datastore

----] E, [2016-11-11T13:19:36.343607 #31592:fc998c] ERROR -- : Couldn't open disk file: [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk
[----] E, [2016-11-11T13:19:36.343876 #31592:fc998c] ERROR -- : Unable to mount filesystem.  Reason:[FFI::VixDiskLib::ApiWrapper#open (errcode=18000 - VIX_E_CANNOT_CONNECT_TO_HOST): Cannot connect to the host - [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk] for VM [[BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmx]
[----] E, [2016-11-11T13:19:36.357310 #31592:fc998c] ERROR -- : MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm) ScanMetadata error status:[16]:  message:[Unable to mount filesystem.  Reason:[FFI::VixDiskLib::ApiWrapper#open (errcode=18000 - VIX_E_CANNOT_CONNECT_TO_HOST): Cannot connect to the host - [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk]]
[----] E, [2016-11-11T13:19:45.240115 #3243:fc998c] ERROR -- : Q-task_id([4be0a774-a83b-11e6-9b09-005056ac33fd]) MIQ(VmScan#process_abort) job aborting, Unable to mount filesystem.  Reason:[FFI::VixDiskLib::ApiWrapper#open (errcode=18000 - VIX_E_CANNOT_CONNECT_TO_HOST): Cannot connect to the host - [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk]
[----] E, [2016-11-11T13:53:59.115706 #2768:fc998c] ERROR -- : Couldn't open disk file: [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk
[----] E, [2016-11-11T13:53:59.127777 #2768:fc998c] ERROR -- : Unable to mount filesystem.  Reason:[FFI::VixDiskLib::ApiWrapper#open (errcode=18000 - VIX_E_CANNOT_CONNECT_TO_HOST): Cannot connect to the host - [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk] for VM [[BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmx]
[----] E, [2016-11-11T13:53:59.409123 #2768:fc998c] ERROR -- : MIQ(ManageIQ::Providers::Vmware::InfraManager::Vm#scan_via_miq_vm) ScanMetadata error status:[16]:  message:[Unable to mount filesystem.  Reason:[FFI::VixDiskLib::ApiWrapper#open (errcode=18000 - VIX_E_CANNOT_CONNECT_TO_HOST): Cannot connect to the host - [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk]]
[----] E, [2016-11-11T13:54:14.170333 #3243:fc998c] ERROR -- : Q-task_id([0fe79480-a840-11e6-9b09-005056ac33fd]) MIQ(VmScan#process_abort) job aborting, Unable to mount filesystem.  Reason:[FFI::VixDiskLib::ApiWrapper#open (errcode=18000 - VIX_E_CANNOT_CONNECT_TO_HOST): Cannot connect to the host - [BUD-LAB-DS002-SHARED] USTMVBCA902/USTMVBCA902.vmdk]


Version-Release number of selected component (if applicable):
CFME 5.6.2.2
VC 5.5

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 4 Dave Johnson 2016-12-06 16:52:01 UTC
Please assess the impact of this issue and update the severity accordingly.  Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.

Comment 5 Saif Ali 2016-12-09 19:06:26 UTC
Hello Dave, 
This bug can be closed because we fixed the issue by downgrading VDDK.

Comment 6 Dave Johnson 2017-01-12 19:01:46 UTC
Which version of the vddk were you using and what did you downgrade too?

Comment 7 Saif Ali 2017-01-12 19:36:43 UTC
It was VDDK 5.5.5, and downgraded to VDDK 5.5.3

Comment 8 Dave Johnson 2017-07-14 01:19:05 UTC
Closing per comment 5


Note You need to log in before you can comment on or make changes to this bug.