-
Notifications
You must be signed in to change notification settings - Fork 339
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Disk not resized when vmware vm scsi controller is "lsi logic" and vm is powered on #1595
Comments
I don't think this is really a problem with resizing, I think it's something else. Could you please add |
That did the trick!
|
It looks like the module tries to change the type to community.vmware/plugins/modules/vmware_guest_disk.py Lines 863 to 872 in de8e030
This is a bit... well, unexpected. I think the module shouldn't try to change the type to I'm not sure yet what I should do about this. But at least you have a workaround now. |
Interesting I added scsi_type: lsilogic and still get the same issue. |
SUMMARY
Disk not resized when vmware vm scsi controller is "lsi logic" and vm is powered on
ISSUE TYPE
COMPONENT NAME
vmware_guest_disk
ANSIBLE VERSION
COLLECTION VERSION
Partial list:
CONFIGURATION
OS / ENVIRONMENT
Rocky 9.1
STEPS TO REPRODUCE
VM is deployed from template where SCSI controller is set to "LSI Logic". Deployment is successful. Vmware tools are pre-installed. VM gets powered ON.
Next step is to modify additional disk, which fails (see below). At the same time resizing disk disk directly from VmWare Vsphere Web console resizing works as expected (disk is resized without any problems).
Solution is to change SCSI controller to be "VmWare Paravirtual". Without any change in playbooks everything works.
where "disks" are defined in external json file like this:
EXPECTED RESULTS
VM disk attached to "LSI Logic" will be resized regardless vm is powered "on" or "off".
It did work with older ansible (centos 7 & ansible 2.9).
ACTUAL RESULTS
Task fails with message: "Parameters for device 'scsi0' may not be modified while the virtual machine is powered on."
The text was updated successfully, but these errors were encountered: