VNFc retry error on when a resource creation fail

[Kenta Fukaya]

When a volume-boot VNFc fails due to insufficient resources,
retry fails because the volume remains in the "reserved" state.

[Yasufumi Ogawa (yasufum)]

https://review.opendev.org/c/openstack/tacker/+/890869

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tacker/+/890869
Committed: https://opendev.org/openstack/tacker/commit/83a109f765be5fc10d19deddadc52f70cb85747b
Submitter: "Zuul (22348)"
Branch: master

commit 83a109f765be5fc10d19deddadc52f70cb85747b
Author: Ken Fujimoto <email address hidden>
Date: Sun Aug 6 11:40:01 2023 +0000

    Add rollback option to create and update stacks

    This patch adds a rollback option to create and update stacks.
    If "CONF.v2_vnfm.enable_rollback_stack" is True,
    when a resource creation fails in the create and update stack,
    rollback stack is executed and the create resource is deleted.
    This feature is implemented to successful AZ reselection at
    the VDU using volume.

    Closes-Bug: #2034886
    Change-Id: Icdc70f299c65a137672935338dd6d795a3dbea73

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tacker 10.0.0.0rc1 release candidate.