Project

General

Profile

Bug #29848

Disks on VMWare VMs can't be provisioned to all possible variations offered by UI

Added by Ondřej Ezr 3 months ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - VMware
Target version:
-
Difficulty:
Triaged:
No
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1750758

Description of problem:

VMWare VM is being provisioned but the disks are assigned from non-selected(while provisioning) data store.

Steps to Reproduce:
----------------

1. Attempt to provision a VM on VMWare.
2. Select 1 disk from DataStore.
3. Select another from Storage Pod - iSCSI cluster.
4. Provision the VM.

Actual Behavior:
----------------
1. VM is provisioned but both the disks are assigned from non-selected(while provisioning) data store - recomended from the Storage Pod selection
2. This also includes the iSCSI cluster storage pod disk is not being selected.

Attaching before and after screenshots disks selected on provisioning.

Expected Behavior:
---------------------
Foreman doesn't offer unsupported selection - if one Storage Pod is selected, other disks can't be selected from Datastores

Note:
-----------
The recommendation is not stated anywhere, so in UI there is no clear visibility how was the datastore selected
This could include the selection of the VM storage first and change allowed on disk bases only when strictly reqired by user.

Also available in: Atom PDF