Bug #3750
Cloning oVirt VMs doesn't create a new disk
Status:
Ready For Testing
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.
Related issues
History
#1
Updated by Dominic Cleal about 6 years ago
Updated by - Related to Bug #3665: Cloning Ovirt based hosts causes the VM disk to be in Illegal state added
#2
Updated by Yama Kasi almost 6 years ago
Updated by 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.
#3
Updated by Dominic Cleal over 5 years ago
- Related to Bug #5581: oVirt image based deployment does not create a disk added
#4
Updated by Dominic Cleal over 5 years ago
- Category set to Compute resources
#5
Updated by Dominic Cleal about 5 years ago
- Category changed from Compute resources to Compute resources - oVirt
#6
Updated by Davide Ferrari over 2 years ago
Updated by 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
#7
Updated by Ori Rabin over 2 years ago
Updated by - Related to Bug #10273: Create VM from image with preallocated disk (oVirt) added
#8
Updated by Bernhard Suttner about 1 year ago
Updated by Isn't this a duplicate of https://projects.theforeman.org/issues/10273?
#9
Updated by Shira Maximov 19 days ago
Updated by - Assignee set to Shira Maximov
#10
Updated by The Foreman Bot 10 days ago
Updated by - Status changed from New to Ready For Testing
- Pull request https://github.com/theforeman/foreman/pull/7207 added