Ramdisk setting in template not recognized
|Assignee:||Ruben S. Montero||% Done:|
|Category:||Core & System|
|Target version:||Release 4.2|
|Affected Versions:||OpenNebula 4.0|
When a Ramdisk is set in the OS section of a VM template, it does not actually get utilized (the file is never copied or added to the VM config) because the transfer manager is looking for a template setting called initrd when it should be looking for INITRD. Attached is a tiny patch for TransferManager.cc to fix the issue.
#1 Updated by Ruben S. Montero about 6 years ago
- Category set to Core & System
- Status changed from Pending to Closed
- Assignee set to Ruben S. Montero
- Target version changed from Release 4.0.1 to Release 4.2
- Resolution set to fixed
Thanks for this!. Tests are based only on the KERNEL attribute... Committed to master and one-4.0 branches.