We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When removing one or more disks and exceeding pool free space we have a poorly formatted user targeted error message:
"Removing disks ([u'virtio-1']) may shrink the pool by ... KB, which is greater than available free space ... KB. This is not supported."
Due to a literal dumping of the Python list type containing one or more disk names to be removed.
It is proposed that we instead present the more user friendly:
"Removing disk/s (virtio-1) may shrink the pool by ... KB, which is greater than available free space ... KB. This is not supported."
with it's mult-disk counterpart of:
"Removing disk/s (virtio-1 virtio-2) may shrink the pool by ... KB, which is greater than available free space ... KB. This is not supported."
The proposed code change to be submitted against this issue already has test counterparts in the ongoing work against issue #2384.
The text was updated successfully, but these errors were encountered:
Improve disk removal error message formatting re pool free space rock…
742229a
…stor#2388 Avoid literal dumping of the Python list type containing one or more disk names to-be-removed into user facing error message.
Merge pull request #2389 from phillxnet/2388_Improve_disk_removal_err…
387fd27
…or_message_formatting_re_pool_free_space Improve disk removal error message formatting re pool free space #2388
Closing as: Fixed by #2389
Sorry, something went wrong.
phillxnet
No branches or pull requests
When removing one or more disks and exceeding pool free space we have a poorly formatted user targeted error message:
Due to a literal dumping of the Python list type containing one or more disk names to be removed.
It is proposed that we instead present the more user friendly:
with it's mult-disk counterpart of:
The proposed code change to be submitted against this issue already has test counterparts in the ongoing work against issue #2384.
The text was updated successfully, but these errors were encountered: