The work in Octavia is complete for adding provisioning status to all of the 
objects.  We just need to make sure that is available via the APISs and clients.
Provisioning status work was done here:

** Project changed: neutron => octavia

You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.

  Heat engine doesn't detect lbaas listener failures

Status in heat:
Status in octavia:

Bug description:
  Please refer to the mail-list for comments from other developers,

  I am trying to use heat to launch lb resources with Octavia as backend. The
  template I used is from

  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.

  3. The bug is introduce from here,
  It only checks the provisioning status of the root loadbalancer.
  However the listener itself has its own provisioning status which may
  go into ERROR.

  4. The same scenario applies for not only listener but also pool,
  member, healthmonitor, etc., basically every resources except
  loadbalancer from lbaas.

To manage notifications about this bug go to:

Mailing list:
Post to     :
Unsubscribe :
More help   :

Reply via email to