I’m trying to bootstrap a juju controller in vsphere with a 300GB root-disk as:
juju bootstrap vmware01-prod prod-infra-e
--config config.yaml
--bootstrap-constraints="mem=32G cores=8 root-disk=300G"
--model-default model-default.yaml
--debug
13:54:18 DEBUG juju.provider.vmware environ_broker.go:234 attempting to create VM in availability zone SeSoVIC847
13:54:18 DEBUG juju.provider.vmware vmdk.go:115 uploading http://cloud-images.ubuntu.com/releases/server/releases/bionic/release-20190307/ubuntu-18.04-server-cloudimg-amd64.ova contents to juju-vmdks/e48bd9af-c8eb-48bd-8d94-74356e969e37/bionic/5dbe1a33f923d549fe9aa45863362f0f68a9524e3feddcf97eb60086be762ebe.vmdk.tmp
13:55:10 DEBUG juju.provider.vmware createvm.go:367 network device: &{VirtualVmxnet:{VirtualEthernetCard:{VirtualDevice:{DynamicData:{} Key:0 DeviceInfo:<nil> Backing:0xc42035b740 Connectable:0xc421dd21c0 SlotInfo:<nil> ControllerKey:0 UnitNumber:<nil>} AddressType:Manual MacAddress:00:50:56:32:11:4e WakeOnLanEnabled:0xc422c14ac0 ResourceAllocation:<nil> ExternalId: UptCompatibilityEnabled:<nil>}}}
13:55:10 DEBUG juju.provider.vmware createvm.go:187 creating temporary VM in folder Folder:group-v600451 @ /Sodertalje-HPC/vm/Juju Controller (e48bd9af-c8eb-48bd-8d94-74356e969e37)/Model "controller" (bfa553fa-9350-44b8-8f38-c763de15b2f4)
13:55:12 DEBUG juju.provider.vmware createvm.go:211 cloning VM
- extending disk to 300GiB
The command never completes but hangs at the - extending disk to 300GiB
I have successfully deployed a juju controller before exactly like this and I’m not sure where and how to debug this.
Leaving out the “root-disk=300G” produces the controller correctly, but I need the disk to be 300GB for the controller.
==============
[SOLUTION] It seems that permissions needs to be properly set in vsphere.