Github user likitha commented on the pull request:
https://github.com/apache/cloudstack/pull/541#issuecomment-117559997
Thanks for taking the time to review @wilderrodrigues.
I have updated the issue description.
As far as 'StorageAction.DELETEVOLUME' is concerned I am not entirely sure
if the same logic applies to HyperV, In case of VMware since we can't access
volume managed object, we reconfigure the VM managed object to detach the
volume and further delete it. And that is why we choose the endpoint based on
the VM. I am not sure if we have the same problem in HyperV. In any case I will
open a ticket to track it, that way we a HyperV expert can comment on it.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at [email protected] or file a JIRA ticket
with INFRA.
---
