Bug 1216900

Summary: Long filename support for Windows VM payload
Product: Red Hat Enterprise Virtualization Manager Reporter: rhev-integ
Component: vdsmAssignee: Eldan Shachar <eshachar>
Status: CLOSED ERRATA QA Contact: Israel Pinto <ipinto>
Severity: unspecified Docs Contact:
Priority: high    
Version: 3.5.0CC: ankit, bazulay, clasohm, david.costakos, ecohen, gklein, lpeer, lsurette, michal.skrivanek, yeylon, ylavi
Target Milestone: ---Keywords: ZStream
Target Release: 3.5.3   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: virt
Fixed In Version: vdsm-4.16.16-1.el6ev Doc Type: Bug Fix
Doc Text:
Cause: Payload ISO's were generated without the Joliet extension. Consequence: Payloads with long filenames weren't displayed correctly on windows systems. Fix: Payloads are now generated along with the Joliet extension. Result: Payloads with long filenames are now displayed correctly on both windows and linux systems.
Story Points: ---
Clone Of: 1205058 Environment:
Last Closed: 2015-06-15 13:19:11 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: Virt RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 1205058    
Bug Blocks:    

Comment 2 Ilanit Stein 2015-04-29 12:09:54 UTC
Can be verified via REST api, by testing first VM CD payload, with filename longer than 15 chars, on version prior to this bug fix, see that it fails.
Then check the same with this bug fix, and see it is indeed supported. 

Added qe_test_coverage flag:
Need to add this test case to VM payload testing.

Comment 7 Israel Pinto 2015-05-17 15:09:19 UTC
Verify with:
RHEVM version: 3.5.3 -vt15
VDSM Version: vdsm-4.16.16-1.el6ev

1. Create 2 VM: Windows7 and RHEL-7.1
2. Add payload via rest with the long file name (more then 15 chars) to each VM like: ABcdefg_xyz_ooo_1234.txt
3. Check payload on VM.

On both OS the file name is as configure.

Comment 9 errata-xmlrpc 2015-06-15 13:19:11 UTC
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.