On Wed, Jul 26, 2017 at 5:34 PM, <mihaela.ba...@orange.com> wrote: > Hello, > > > > Is Octavia (Ocata version) supposed to work with Heat (tested with Newton > version) deployment? I launch a Heat stack trying to deploy a load balancer > with a single listener/pool and two members. While the Heat shows status > COMPLETE and the Neutron shows all objects as created, Octavia creates the > listener, the pool but with a single member (instead of two). > > Another example: I launch a Heat stack trying to deploy a load balancer > with a multiple listeners/pools each having two members. The results is > that Heat shows status COMPLETE and the Neutron shows all objects as > created, Octavia creates the listeners, but only some of the pools and for > those pool creates only one member or none. > > In the Octavia log I could see only these type of errors: > > Sounds like https://bugs.launchpad.net/heat/+bug/1632054.
We just check provisioning_status of the loadbalancer when adding members and mark the resource as CREATE_COMPLETE. I think octavia had added provisioning_status for all top level objects like listener etc[1], but I don't think those attributes are available with lbaasv2 api for us to check. [1] https://review.openstack.org/#/c/372791/ > > 2017-07-26 08:12:08.639 1 INFO octavia.api.v1.controllers.member > [req-749be397-dd63-4fb6-9d86-b717f6d59e3d - 989bbadfe4134722b478ca799217833e > - default default] Member cannot be created or modified because the Load > Balancer is in an immutable state > > 2017-07-26 08:12:08.698 1 DEBUG wsme.api > [req-749be397-dd63-4fb6-9d86-b717f6d59e3d > - 989bbadfe4134722b478ca799217833e - default default] Client-side error: > Load Balancer b12a29db-81d0-451a-af9c-d563b636bf01 is immutable and > cannot be updated. format_exception /opt/octavia/lib/python2.7/ > site-packages/wsme/api.py:222 > > > > I think what happens is that it takes some time until the configuration is > updated on an amphora and during that time the Load Balancer is in UPDATE > state and new configuration cannot be added. > > > > Is this scenario validated or it is still work in progress? > > > > Thanks, > > Mihaela Balas > > > > > > _________________________________________________________________________________________________________________________ > > Ce message et ses pieces jointes peuvent contenir des informations > confidentielles ou privilegiees et ne doivent donc > pas etre diffuses, exploites ou copies sans autorisation. Si vous avez recu > ce message par erreur, veuillez le signaler > a l'expediteur et le detruire ainsi que les pieces jointes. Les messages > electroniques etant susceptibles d'alteration, > Orange decline toute responsabilite si ce message a ete altere, deforme ou > falsifie. Merci. > > This message and its attachments may contain confidential or privileged > information that may be protected by law; > they should not be distributed, used or copied without authorisation. > If you have received this email in error, please notify the sender and delete > this message and its attachments. > As emails may be altered, Orange is not liable for messages that have been > modified, changed or falsified. > Thank you. > > > __________________________________________________________________________ > 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 > >
__________________________________________________________________________ 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
