You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 9, 2020. It is now read-only.
Then tried to revert the --volume-maxsize to the way it was - revert it back to Unset.
Basically I again wanted to make volume-maxsize as unlimited for _DEFAULT tenant - Failed.
Ideally, we shouldn't see a stack trace if a particular command fails.
Tried to revert the --volume-maxsize to the way it was - revert it back to Unset.
[root@sc-rdops-vm04-dhcp-100-33:~] /usr/lib/vmware/vmdkops/bin/vmdkops_admin.py vmgroup access set --name=_DEFAULT --datastore=_VM_DS --allow-create=True --volume-maxsize=Unset
Traceback (most recent call last):
File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 1406, in <module>
main()
File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 61, in main
args.func(args)
File "/usr/lib/vmware/vmdkops/bin/vmdkops_admin.py", line 1083, in tenant_access_set
volume_maxsize_in_MB = convert.convert_to_MB(args.volume_maxsize)
File "/usr/lib/vmware/vmdkops/Python/convert.py", line 27, in convert_to_MB
value = int(vol_size_str[:-2])
ValueError: invalid literal for int() with base 10: 'Uns'
[root@sc-rdops-vm04-dhcp-100-33:~]
The text was updated successfully, but these errors were encountered:
ashahi1
changed the title
Command to set max-volume-size for vmgroup fails if string is specified as size
Command to set max-volume-size for vmgroup fails if size is specified as string
Jun 13, 2017
Steps:
Basically I again wanted to make volume-maxsize as unlimited for _DEFAULT tenant - Failed.
Ideally, we shouldn't see a stack trace if a particular command fails.
===================
Steps and their output are as follows:
The text was updated successfully, but these errors were encountered: