It's a bug in the logic of deleting datastore files.ĭuring vic-machine-linux delete, it cleans up all the datastore files in the VCH's datastore folder. Pinging relevant people for better do you happen to know the potential reasons why deleting datastore files fail? what additional information do we need to identify the root cause in this particular scenario? The error message Cannot delete file virtual-container-host in the log isn't very informational (and that should probably be improved).
Hopefully that will fix things in the future.īut I'm not sure as for the underlying root cause of why deleting datastore files failed. I'm working on fixing the bug to avoid unnecessary VM unregister and datastore file cleanup. This process is probably not what it should be - there's a bug on our side that we disable destroy operation on VM at some point but we never re-enable it, so step 1 fails every time, and we end up doing unregister every time, and that's error prone since there're cases like yours where deleting datastore files fails. In your case, step 1 fails because of a MethodDisabledError from vSphere, and it goes to step 2, and then step 3 fails. If step 2 succeeds, manually cleanup all the datastore files (since unregister doesn't delete datastore files).If step 1 fails, unregister the VM instead.
#UNABLE TO DELETE FLAT VMDK FILES FROM DATASTORE UPDATE#
INFO To modify firewall rules see vic-machine update firewall -helpĪs far as I know the whole delete VCH process goes like this: INFO If firewall changes were made for VIC during install, they were not reverted during delete INFO Removing Resource Pool "virtual-container-host" INFO Unregistered VM to cleanup after failed destroy: "VirtualMachine:vm-126"ĭEBU Failed to delete " virtual-container-host": Cannot delete file virtual-container-host
0 kommentar(er)
