Actions
Bug #3750
closedCloning oVirt VMs doesn't create a new disk
Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - oVirt
Target version:
-
Description
When you select clone within foreman and the provisioner is using oVirt, it'll populate all the fields including the disk, however when it goes to actually provisioning the VM the disk is not created. So it ends up with a cloned configuration replica without a disk.
Updated by Dominic Cleal almost 11 years ago
- Related to Bug #3665: Cloning Ovirt based hosts causes the VM disk to be in Illegal state added
Updated by Yama Kasi almost 11 years ago
This bug is still available in 1.4 RC2
Note: When adding a disk after to this cloned VM using FM the disk will not be activated automaticly in oVirt.
Updated by Dominic Cleal over 10 years ago
- Related to Bug #5581: oVirt image based deployment does not create a disk added
Updated by Dominic Cleal about 10 years ago
- Category changed from Compute resources to Compute resources - oVirt
Updated by Davide Ferrari over 7 years ago
This is still the case for Foreman 1.14.3 (and probably for 1.15 too, current stable version as of writing). Basically it's impossible to do any ovirt disk-related task with Foreman
Updated by Ori Rabin about 7 years ago
- Related to Bug #10273: Create VM from image with preallocated disk (oVirt) added
Updated by Bernhard Suttner almost 6 years ago
Isn't this a duplicate of https://projects.theforeman.org/issues/10273?
Updated by The Foreman Bot almost 5 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7207 added
Updated by Shira Maximov over 4 years ago
- Status changed from Ready For Testing to Closed
Applied in changeset e865ef116baa789d312cd2b57f635aad3e93ad99.
Actions