When growing an existing guest's virtual disk, the ESXi web interface is not updated to show the correct storage capacity. This only happens on update operations and not create operations because create eventually reloads the guest (vim-cmd vmsvc/reload).
Note: This bug does not directly impact resources using the provider because the disk size is determined directly.
This does 2 things:
Creates a guestReload function (similar to guestPowerOn), and refactors existing code to use it
Calls guestReload when a guest disk is successfully expanded after growVirtualDisk
When growing an existing guest's virtual disk, the ESXi web interface is not updated to show the correct storage capacity. This only happens on update operations and not create operations because create eventually reloads the guest (
vim-cmd vmsvc/reload
).Note: This bug does not directly impact resources using the provider because the disk size is determined directly.
This does 2 things:
guestReload
function (similar toguestPowerOn
), and refactors existing code to use itguestReload
when a guest disk is successfully expanded aftergrowVirtualDisk