Updated proper response for no records while executing purge command

[pjsharath28]

This fix is to maintain consistency in response of purge command responses. When we are trying to purge and there is no response, purge networks and purge images are providing no data found response whereas purge vms and purge volumes are providing empty table. As part of this fix we are trying to fix the issue.

Before

After

[ppc64le-cloud-bot]

Welcome @pjsharath28! It looks like this is your first PR to ppc64le-cloud/pvsadm 🎉

[ppc64le-cloud-bot]

Hi @pjsharath28. Thanks for your PR.

I'm waiting for a ppc64le-cloud 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.

[kishen-v]

/ok-to-test

[kishen-v]

/lgtm

[mkumatag]

/lgtm

[ppc64le-cloud-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mkumatag, pjsharath28

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mkumatag]

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