Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1441727 - Smartstate Analysis Error Unable to mount filesystem Unable to determine port used by VixDiskLib VMware
Smartstate Analysis Error Unable to mount filesystem Unable to determine port...
Status: CLOSED ERRATA
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis (Show other bugs)
5.7.0
All All
high Severity high
: GA
: 5.7.3
Assigned To: Jerry Keselman
Satyajit Bulage
smartstate:vmware:vm
: ZStream
Depends On: 1432679
Blocks:
  Show dependency treegraph
 
Reported: 2017-04-12 10:46 EDT by Satoe Imaishi
Modified: 2017-06-28 10:59 EDT (History)
10 users (show)

See Also:
Fixed In Version: 5.7.3.1
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1432679
Environment:
Last Closed: 2017-06-28 10:59:55 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: VMware


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2017:1601 normal SHIPPED_LIVE Important: CFME 5.7.3 security, bug fix and enhancement update 2017-06-28 14:51:52 EDT

  None (edit)
Comment 4 Satyajit Bulage 2017-06-16 10:33:17 EDT
After performing SSA on some VMs, not getting "Unable to mount filesystem. Reason:[ERROR: VixDiskLib.connect() Unable to determine port used by VixDiskLib Server.]" using vddk6.5 but getting other issue and logged separate BZ for it.

Based on this verifying it.

Verified version: 5.7.3.1.20170608124102_4b35a9e
Comment 6 errata-xmlrpc 2017-06-28 10:59:55 EDT
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:1601

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