Complete deletion of CnsFileAccessConfig instance if associated nodeVM instance is not found

[vdkotkar]

What this PR does / why we need it:
If nodeVM instance is deleted and later we get request to delete CnsFileAccessConfig instance, then currently we return error and cnsfileaccessconfig instance never gets deleted.
Updating code to proceed with the deletion of cnsfileaccessconfig instance if the associated nodeVM instance is not found (already deleted).

Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #

Testing done:
make check and make test are passing.

Special notes for your reviewer:

Release note:

Complete deletion of CnsFileAccessConfig instance if associated nodeVM instance is not found

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vdkotkar
Once this PR has been reviewed and has the lgtm label, please assign xing-yang for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[k8s-ci-robot]

Hi @vdkotkar. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[divyenpatel]

/ok-to-test

[chethanv28]

If we return success here, we will miss the deletePermission on the fileshare.

I think we need to invoke
"err = r.configureNetPermissionsForFileVolume(ctx, volumeID, vm, instance, true)".

I'm not sure how you can fetch the vm info though.

[vdkotkar]

Yes, since VM is already deleted we won't get VM object. So, it is not possible to run configureNerPermissionsForFileVolume. I am also not sure if we can do anything else here.
@divyenpatel Can you please review these changes once.