-
Notifications
You must be signed in to change notification settings - Fork 915
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] Unable to run govc disk.ls or govc disk.ls -R #3639
Comments
Howdy 🖐 jespinosaitrs ! 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 |
Please update the title from |
@tenthirtyam Sorry about that, I forgot to put something in it. |
@jespinosaitrs what is your vCenter version? How are your disks created and managed, CNS Volumes or ? Either way, we can add a flag to change the error to warning and/or ignored as discussed here: |
@dougm Here are the details:
As for the disks, I would say most of them are CNS volumes. And as long as the tool can output the list of disk I'm fine with any fixes. What I'm trying to do is some scripting to identify and cleanup some orphan disks but not getting even a partial output is making that difficult. |
Deleting an FCD file backing can create an orphan FCD. An orphaned ID is returned by the ListVStorageObject API, but calling RetrieveVStorageObject with an orphan ID results in a NotFound fault. The disk.ls command would return an error and suggest: use 'disk.ls -R' to reconcile datastore inventory The -R flag calls ReconcileDatastoreInventory, which normally cleans up such orphans, but we have seen cases where it does not. This change ignores orphans by default. The new '-a' flag will list *all* orphans (if any) and includes the disk.ls -R suggestion. Fixes vmware#3639 Signed-off-by: Doug MacEachern <dougm@broadcom.com>
Deleting an FCD file backing can create an orphan FCD. An orphaned ID is returned by the ListVStorageObject API, but calling RetrieveVStorageObject with an orphan ID results in a NotFound fault. The disk.ls command would return an error and suggest: use 'disk.ls -R' to reconcile datastore inventory The -R flag calls ReconcileDatastoreInventory, which normally cleans up such orphans, but we have seen cases where it does not. This change ignores orphans by default. The new '-a' flag will list *all* orphans (if any) and includes the disk.ls -R suggestion. Fixes vmware#3639 Signed-off-by: Doug MacEachern <dougm@broadcom.com>
@jespinosaitrs please review #3659 |
Describe the bug
I am unable to run
govc disk.ls
orgovc disk.ls -R
. Both fail with the same error:To Reproduce
Steps to reproduce the behavior:
govc disk.ls
orgovc disk-ls -R
.govc: 0b5dfeb3-3b76-44c0-a183-6e082734eba5 not found: use 'disk.ls -R' to reconcile datastore inventory
is shown.Expected behavior
The commands should finish without errors and display the disks or reconcile the disks.
Affected version
Screenshots/Debug Output
Additional context
There are two other identical issues in the repository that were marked as closed:
The text was updated successfully, but these errors were encountered: