Project

General

Custom queries

Profile

Actions
Copy link

Bug #3750

closed

Cloning oVirt VMs doesn't create a new disk

Added by Andrew Lau over 11 years ago. Updated about 5 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Shira Maximov
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
https://github.com/theforeman/foreman/pull/7207
Fixed in Releases:
2.1.0
Found in Releases:
Red Hat JIRA:

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 3 (0 open — 3 closed)

Related to Foreman - Bug #3665: Cloning Ovirt based hosts causes the VM disk to be in Illegal stateDuplicateActions
Related to Foreman - Bug #5581: oVirt image based deployment does not create a diskClosedActions
Related to Foreman - Bug #10273: Create VM from image with preallocated disk (oVirt)ClosedOri Rabin04/27/2015Actions
Actions
Copy link
 #2

Updated by Yama Kasi about 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.

Actions
Copy link
 #6

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

Actions
Copy link
 #12

Updated by Shira Maximov about 5 years ago

  • Status changed from Ready For Testing to Closed
Actions
Copy link

Also available in: Atom PDF