Bug #5288

Support spaces in VMDK names and dirnames

Added by Tino Vázquez 3 months ago. Updated about 1 month ago.

Status:ClosedStart date:07/26/2017
Priority:NormalDue date:
Assignee:Jaime Melis% Done:

0%

Category:vCenter
Target version:Release 5.4.1
Resolution:fixed Pull request:
Affected Versions:Development

Description

This prevents the use and import of VMs and VM Templates with disks with spaces


Related issues

Related to Bug #4514: Spaces not allowed in SOURCE image attribute Closed 06/01/2016

Associated revisions

Revision 33fa9c9d
Added by Jaime Melis about 1 month ago

B #5288: Support spaces in VMDK names and dirnames

Revision abe4dc2c
Added by Jaime Melis about 1 month ago

B #5288: Support spaces in VMDK names and dirnames

(cherry picked from commit 33fa9c9ddec85797dade89ec9793ed7f00f9ea83)

Revision 0596d791
Added by Jaime Melis about 1 month ago

B #5288: Support spaces in premigrator

Revision 96f1d9d3
Added by Jaime Melis about 1 month ago

B #5288: premigrator does not fail if images have been deleted from
vcenter

Revision 02b9fe78
Added by Jaime Melis about 1 month ago

B #5288: Support spaces in premigrator

(cherry picked from commit 0596d7917ea4c1781c101c73645ec329620a70c3)

Revision 20795566
Added by Jaime Melis about 1 month ago

B #5288: premigrator does not fail if images have been deleted from
vcenter

(cherry picked from commit 96f1d9d3365d4f04b0564fdd4be80a6b156d8fac)

History

#1 Updated by Jaime Melis about 1 month ago

  • Related to Bug #4514: Spaces not allowed in SOURCE image attribute added

#2 Updated by Jaime Melis about 1 month ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

Also available in: Atom PDF