Description of problem: Install vsphere/ipi on ocp4.5 nightly build, after generating install-config through command "openshift-install create install-config, and update install-config to customize cpu,memory and disksize of master node and worker node, then continue installation, the disksize of master is always 120G. After checking code, it is hard coded. https://github.com/openshift/installer/blob/master/data/data/vsphere/master/main.tf#L23 How reproducible: 100% Steps to Reproduce: 1. run command "openshift-install create install-config" to generate install-config file 2. update install-config.yaml file to customize cpu,memory and disksize of master node and worker node -------- apiVersion: v1 baseDomain: qe.devcluster.openshift.com compute: - hyperthreading: Enabled name: worker replicas: 2 platform: vsphere: cpus: 4 coresPerSocket: 2 memoryMB: 4096 osDisk: diskSizeGB: 50 controlPlane: hyperthreading: Enabled name: master replicas: 3 platform: vsphere: cpus: 4 coresPerSocket: 2 memoryMB: 8192 osDisk: diskSizeGB: 50 ... 3. run command "openshift-install create cluster" to install cluster 4. After vms are created on vsphere server, checked that the disksize on master node is assigned to 120G Actual results: The disk size on master node is assigned to 120G Expected results: The disk size on master node should be one defined in install-config Additional info:
Verified on 4.5.0-0.nightly-2020-05-13-014437, control_plane vm's disk has been set to expected one in customized install-config.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:2409