Project

General

Profile

Actions

Bug #23218

closed

Clone Host results in lost storage

Added by Arend Lapere about 6 years ago. Updated over 5 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
Compute resources - oVirt
Target version:
-
Difficulty:
Triaged:
No
Fixed in Releases:
Found in Releases:

Description

I've created a host, running on an oVirt compute resource. For testing, I wanted to clone this device. At first glance, everything looked fine, it had the same vCPUs, the same amount of RAM and the storage settings were correct as well. However, as soon as the cloning was done, the system auto-provisions itself, complaining about the disk-size. Looking at the settings for that cloned host, I noticed the storage settings were gone (and thus no hard-disk was available for provisioning).

Steps to reproduce ==================
- Set-up ovirt compute resource
- Create host e.g. 1vCPU, 2GB RAM
- Click "clone"
- Observe settings for Virtual Machine: the storage settings are available
- Click "Submit"
- Edit the cloned device
- Observe settings for Virtual Machine: the storage settings are gone (effectively, no storage has been assigned to the host)

Expected result ===============
If the system displays that the storage would be created, it should actually create it

Workaround ==========
- During cloning, remove the storage
- Recreate the storage
- Click submit

Infrastructure ==============
- Foreman
- OS: CentOS 7
- Version: 1.18 (from nightly)
- Installed/configured plugins:
- oVirt compute resource
- ansible
- puppet
- dhcp
- dns
- oVirt
- OS: CentOS 7
- Version: 4.2
- Single node

Actions #1

Updated by Arend Lapere about 6 years ago

  • Status changed from New to Duplicate

Sorry, just saw that this bug was already mentioned a few months ago.

Actions #2

Updated by Ewoud Kohl van Wijngaarden over 5 years ago

  • Target version deleted (1.18.0)
  • Triaged set to No
Actions

Also available in: Atom PDF