On Wed, Sep 28, 2016 at 6:21 AM, Jiahao Liang < jiahao.li...@oneconvergence.com> wrote:
> > > On Tue, Sep 27, 2016 at 5:35 PM, Rabi Mishra <ramis...@redhat.com> wrote: > >> On Wed, Sep 28, 2016 at 1:01 AM, Zane Bitter <zbit...@redhat.com> wrote: >> >>> On 27/09/16 15:11, Jiahao Liang wrote: >>> >>>> 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. >>>> >>> >>> That sounds like a clear bug. >>> >> >> It seems we're checking for any exceptions from the client[1], before >> checking for the >> loadbalancer status. I could not see any other way to check the listener >> status afterwards. >> Probably a lbaas bug with octavia driver? >> >> Could you please raise a bug with the heat/lbaas logs? >> > >> [1] https://git.openstack.org/cgit/openstack/heat/tree/heat/engi >> ne/resources/openstack/neutron/lbaas/listener.py#n183 >> > > In Octavia, creating resources (listeners, pools, etc.) is an async > operation which it wouldn't raise any exception. > A normal workflow is: > 1. heat/neutron client send a create api to Octavia > 2. Octavia return a response to client and set the resource to > PENDING_CREATE (no exception will throw to client if the api goes through.) > 3. It creation succeeds, Octavia set that resource to ACTIVE; otherwise, > set it to ERROR. > Unlike loadbalancer, I don't see any provisioning_status attribute for listener in lbaas api[1]. [1] http://git.openstack.org/cgit/openstack/neutron-lbaas/tree/neutron_lbaas/extensions/loadbalancerv2.py#n192
__________________________________________________________________________ OpenStack Development Mailing List (not for usage questions) Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
