Project

General

Profile

Actions

Bug #9705

closed

Disk sizes specified not used in VMware image provisioning

Added by Bryan Kearney over 9 years ago. Updated over 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Compute resources - VMware
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Customer clones host in Vmware ESX cluster from template. Template has two disks attached. In Sat6 WebUI customer adjusts size of disks to be attached to the VM but newly created host ignores supplied values and create VM with same disk size as template.

Version-Release number of selected component (if applicable):

How reproducible:

Steps to Reproduce:
  • in VMware UI create template based on image. Image must have some disk(s) attached.
  • In Sat6 define VMware compute resource and some compute profiles * Make compute profiles using VMware template defined before * In satellite6 WebUI go Hosts->New Host. * Fill all needed parameters. * Select Deploy on VMware. * Select Compute Profile * in Virtual Machine Tab * in the Volumes section change Size * Click Submit.
    Actual results:
    New host gets same disk(s) size as template had but not the one from the list

Expected results:
Host gets correct type and label assigned to network interface

patches are available downstream


Related issues 4 (1 open3 closed)

Related to Foreman - Bug #9704: Network label is unchanged on additional network interfaces with VMware templatesClosedIvan Necas03/10/2015Actions
Related to Foreman - Bug #12487: Provisioning with Templates causes new VM to use Template DiskNew11/15/2015Actions
Has duplicate Foreman - Bug #10776: computer resource vmware add diskDuplicate06/10/2015Actions
Blocked by Foreman - Refactor #10997: Update fog to 1.33.0ClosedDominic Cleal07/03/2015Actions
Actions

Also available in: Atom PDF