Bug #4514
Spaces not allowed in SOURCE image attribute
Status: | Closed | Start date: | 06/01/2016 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | - | % Done: | 0% | |
Category: | vCenter | |||
Target version: | - | |||
Resolution: | duplicate | Pull request: | ||
Affected Versions: | OpenNebula 5.4 |
Description
When the cp DS driver returns a string with spaces, it is truncated and only the characters up to the first space are set into the SOURCE of the image
Related issues
Associated revisions
Bug #4514: Deal with spaces in vCenter paths
History
#1 Updated by Ruben S. Montero about 5 years ago
- Category changed from Core & System to vCenter
#2 Updated by Tino Vázquez about 5 years ago
- Target version changed from Release 5.0 to Release 5.2
Spaces won't be supported in vCenter paths for import in Wizard 5.0
#3 Updated by Tino Vázquez over 4 years ago
- Target version changed from Release 5.2 to Release 5.4
#4 Updated by Miguel Ángel Álvarez Cabrerizo over 4 years ago
- Target version deleted (
Release 5.4)
#5 Updated by Jaime Melis about 4 years ago
- Tracker changed from Bug to Backlog
- Target version set to Release 5.6
#6 Updated by Jaime Melis almost 4 years ago
- Related to Bug #5288: Support spaces in VMDK names and dirnames added
#7 Updated by Jaime Melis almost 4 years ago
- Tracker changed from Backlog to Bug
- Status changed from New to Closed
- Target version deleted (
Release 5.6) - Resolution set to duplicate
- Affected Versions OpenNebula 5.4 added