vnf package delete should return 409 if operational state is ENABLED and usage state is IN_USE

[Tushar Patil]

If vnf package usage state is IN_USE, vnf package shouldn’t be deleted.

As per 9.3.6 section of SOL005, vnf package should be deleted only if it’s operational state is DISABLED and usage state is NOT_IN_USE.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/707310

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/707310
Committed: https://git.openstack.org/cgit/openstack/tacker/commit/?id=33f92086f4cf7d42ddd51507a1c00c78315ed5c1
Submitter: Zuul
Branch: master

commit 33f92086f4cf7d42ddd51507a1c00c78315ed5c1
Author: tpatil <email address hidden>
Date: Wed Feb 12 02:45:20 2020 +0000

    Delete vnf package if operationalState is DISABLED

    Presently, vnf package can be deleted when it's operationalState is
    'ENABLED'.

    As per pre-condition rule, vnf package can be deleted only when
    it's operationalState is 'DISABLED' and it's usageState is 'NOT_IN_USE.

    This patch fixes this issue and now vnf package will be deleted only
    when it's operationalState is 'DISABLED' and it's usageState is 'NOT_IN_USE.

    Note: I have fixed windows style line ending issue in vnf_packages.inc.
    Also, updated 'Delete VNF Package' API doc to include 409 error.

    Change-Id: Id4d50264d1052a09e6ce527b6aab1bb941fdc6af
    Closes-Bug: #1862864