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