[openstack-dev] [neutron][lbaas][heat][octavia] Heat engine doesn't detect lbaas listener failures

Jiahao Liang jiahao.liang at oneconvergence.com
Tue Sep 27 19:11:37 UTC 2016


Hello all,

I am trying to use heat to launch lb resources with Octavia as backend. The
template I used is from
https://github.com/openstack/heat-templates/blob/master/hot/lbaasv2/lb_group.yaml
.

Following are a few observations:

1. Even though Listener was created with ERROR status, heat will still go
ahead and mark it Creation Complete. As in the heat code, it only check
whether root Loadbalancer status is change from PENDING_UPDATE to ACTIVE.
And Loadbalancer status will be changed to ACTIVE anyway no matter
Listener's status.


2. As heat engine wouldn't know the Listener's creation failure, it will
continue to create Pool\Member\Heatthmonitor on top of an Listener which
actually doesn't exist. It causes a few undefined behaviors.  As a result,
those LBaaS resources in ERROR state are unable to be cleaned up
with either normal neutron or heat api.


Is this a bug regarding LBaaS V2 for heat, or is it designed that way on
purpose?  In my opinion, it would be more natural if heat reports
CREATION_FAILURE if any of the LBaaS resources fails.

Thanks,
Jiahao Liang
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20160927/3ff47533/attachment.html>


More information about the OpenStack-dev mailing list