Bug 1299504 - SSA fails for RHEVM 3.4 VMs on NFS - 'no such file or directory'
SSA fails for RHEVM 3.4 VMs on NFS - 'no such file or directory'
Status: CLOSED WORKSFORME
Product: Red Hat CloudForms Management Engine
Classification: Red Hat
Component: SmartState Analysis (Show other bugs)
5.4.0
Unspecified Unspecified
unspecified Severity unspecified
: GA
: 5.6.0
Assigned To: Mo Morsi
Dave Johnson
:
Depends On:
Blocks: 1300030 1300032
  Show dependency treegraph
 
Reported: 2016-01-18 09:24 EST by Vadim Rutkovsky
Modified: 2016-01-21 10:27 EST (History)
5 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1300030 1300032 (view as bug list)
Environment:
Last Closed: 2016-01-21 10:27:09 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
EVM log (275.33 KB, text/plain)
2016-01-18 09:24 EST, Vadim Rutkovsky
no flags Details

  None (edit)
Description Vadim Rutkovsky 2016-01-18 09:24:35 EST
Created attachment 1115854 [details]
EVM log

Description of problem:
'No such file or directory' error occurs for SSA on rhevm 3.4 vms on NFS storage. The exact configuration works on 5.5

Version-Release number of selected component (if applicable):
cfme-5.4.4.2-1.el6cf.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Add RHEVM provider
2. Spin up a new VM on NFS storage
3. Run smart start analysis for the VM

Actual results:
Task fails - 'No such file or directory - /mnt/vm/dadea2de-bded-11e5-a828-fa163e31958a/rhev/data-center/339f2b7e-8359-4f79-ae24-b2dd70126a97/mastersd/master/vms/5ebec6ad-2e09-40f6-8f49-ae72e0fa666a/5ebec6ad-2e09-40f6-8f49-ae72e0fa666a.ovf for VM:[/rhev/data-center/339f2b7e-8359-4f79-ae24-b2dd70126a97/mastersd/master/vms/5ebec6ad-2e09-40f6-8f49-ae72e0fa666a/5ebec6ad-2e09-40f6-8f49-ae72e0fa666a.ovf]'

Expected results:
SSA task passes, VM details are updated

Additional info:
Comment 2 Rich Oliveri 2016-01-21 10:27:09 EST
This was fixed in 5.5. Fix could not be back-ported to 5.4.

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