-
Notifications
You must be signed in to change notification settings - Fork 911
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
[BUG] vcsim: #2911 mandated to pass the new disk size in Bytes and KB. If either of value is 0, ReconfigVM_Task is throwing *types.InvalidDeviceOperation #3423
Comments
Howdy 🖐 Davinder2me ! Thank you for your interest in this project. We value your feedback and will respond soon. If you want to contribute to this project, please make yourself familiar with the |
Davinder2me
pushed a commit
to Davinder2me/govmomi
that referenced
this issue
Apr 23, 2024
…and KB. If either of value is 0, ReconfigVM_Task is throwing *types.InvalidDeviceOperation Closes: vmware#3423
12 tasks
dougm
pushed a commit
to Davinder2me/govmomi
that referenced
this issue
Apr 24, 2024
CapacityInBytes and the deprecated CapacityInKB fields do not both need to be set. Closes: vmware#3423
dougm
pushed a commit
to Davinder2me/govmomi
that referenced
this issue
Apr 24, 2024
CapacityInBytes and the deprecated CapacityInKB fields do not both need to be set. Closes: vmware#3423
dougm
added a commit
that referenced
this issue
Apr 24, 2024
vcsim: Fix:#3423 - mandated to pass the new disk size in Bytes and KB…
dougm
pushed a commit
that referenced
this issue
May 7, 2024
CapacityInBytes and the deprecated CapacityInKB fields do not both need to be set. Closes: #3423
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
#2911 mandated to pass the new disk size in Bytes and KB. If either of value is 0, ReconfigVM_Task is throwing *types.InvalidDeviceOperation
To Reproduce
Steps to reproduce the behavior:
Expected behavior
ReconfigureVM_task should work with one value of new disk.
Affected version
v0.37.1 and all other releases with b6ebcb6
The text was updated successfully, but these errors were encountered: