juju using vsphere not set the correct hw version using force-vm-hardware-version

[Pedro Victor Lourenço Fragola]

If you bootstrap a Juju controller that defaults to a specific hardware version, such as hardware version 10 for VMware, and then you create a model and set different model-defaults or model-config using the force-vm-hardware-version parameter, it will not work as expected. This is because the template for that VM is using a different hardware version, and Juju is not capable of changing the hardware version of an existing VM template.

Workaround:
To resolve this, you can convert the Juju template to a virtual machine and upgrade the hardware version of the VM. Once the hardware version is updated, convert the VM back into a template.

Juju 3.4.2/stable

[Ian Booth (wallyworld)]

It does seem unfortunate that we expose a model config parameter that is only useful at the time a model is created.