Bug #2147
Ramdisk setting in template not recognized
| Status: | Closed | Start date: | 07/01/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.2 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.0 |
Description
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.
Associated revisions
bug #2147: Fix INITRD attribute name by Tim Moss
bug #2147: Fix INITRD attribute name by Tim Moss
(cherry picked from commit 0ee0edf8947ebefdbc381dc38acbe3cbfca6c56a)
History
#1
Updated by Ruben S. Montero about 8 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.