When an exception occurs in the Exception of lcm operations, then notification is not sent.

[Pooja Singla]

When exception occurs in the exception block during the instantiation, heal, terminate, change external connectivity operations then notification may not be sent because there is no process for handling of further exception which occurs during the exception processing.

[Pooja Singla (psingla)]

I am assigning this bug to me. I will be working on it.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: master
Review: https://review.opendev.org/c/openstack/tacker/+/851508

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.opendev.org/c/openstack/tacker/+/851508
Committed: https://opendev.org/openstack/tacker/commit/3bdb71c8123b8400c62406d168d852b586f0544b
Submitter: "Zuul (22348)"
Branch: master

commit 3bdb71c8123b8400c62406d168d852b586f0544b
Author: Pooja Singla <email address hidden>
Date: Mon Sep 5 07:26:55 2022 +0000

    Handled exception in exception of instantiation

    When exception occurs in exception block of
    instantiation, heal, termination, change external connectivity
    operations then notification was not sent.

    Implemented exception handling in exception block of instantiation,
    heal, termination, change external connectivity operations.

    Closes-Bug: #1983096
    Change-Id: I645e342167d22ac3764cdb20ef1a0f77f801fb95

[OpenStack Infra (hudson-openstack)]

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