Project

General

Profile

Actions

Bug #20458

open

Storage defined in used compute profile can't be removed during image based provisioning

Added by Filip Brychta almost 7 years ago. Updated almost 7 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Steps to reproduce:
1 - create compute profile with one bootable storage on oVirt compute resource
2 - try to create new host using image based provisioning and compute profile from previous step -> it fails with Cannot add Virtual Disk. Disk ... in VM ... is already marked as boot.
3 - remove the storage on Virtual Machine tab
4 - click Submit again -> still the same error -> it's still trying to create the storage defined in compute profile even though it was removed on Virtual Machine tab

It's working fine when no compute profile is used and all values are manually set.

Expected result:
In foreman 1.7.1 when using compute profile and image based provisioning the storage defined in compute profile was not used and UI was showing only storage used by given template (with correct size and storage domain)

Found in versions:
- foreman 1.15.2
- rhev 4.1

Actions #1

Updated by Filip Brychta almost 7 years ago

  • Description updated (diff)
Actions

Also available in: Atom PDF