Bug #4431
Missing VMDKs and wrong size on vCenter importing
| Status: | Closed | Start date: | 04/26/2016 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Tino Vázquez | % Done: | 100% | |
| Category: | vCenter | |||
| Target version: | Release 5.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | Development |
Description
Not all VMDKs are imported, need to research why. Specially those on the root folder.
Also, some VMDKs are stated with the wrong file size (may have to do with flat vmdks)
Associated revisions
Bug #4431: Add datastore suffix to image name in vCenter image import
Bug #4431: Mended CLI to create vCenter datablocks
History
#1
Updated by Tino Vázquez about 5 years ago
- % Done changed from 0 to 80
- There is a limitation of only 1 virtual disk per folder [Documentation]
- A suffix with the name of the datastore is added to the image name to prevent collisions [Done]
- Mended CLI to create datablocks [Done]
- empty datablocks should be on a separate folder (OpenNebulaDisks/<iid>) [Evaluate]
- Disk space should not be checked on importing & registering images (they are already there) [Evaluate]
#2
Updated by Tino Vázquez about 5 years ago
- Status changed from Pending to Closed
- % Done changed from 80 to 100
- Resolution set to fixed
Opened two separate tickets to deal with the remaining issues:
http://dev.opennebula.org/issues/4508
http://dev.opennebula.org/issues/4509