juju using vsphere not set the correct hw version using force-vm-hardware-version
Bug #2064731 reported by
Pedro Victor Lourenço Fragola
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Canonical Juju |
Triaged
|
Wishlist
|
Unassigned |
Bug Description
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-
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
To post a comment you must log in.
It does seem unfortunate that we expose a model config parameter that is only useful at the time a model is created.