Hi Eric, that's exactly what the change I mentioned has done. :-) Kind regards, Radek czw., 17 paź 2019 o 08:20 Eric K. Miller <emiller@genesishosting.com> napisał(a):
Correction - I meant "Kolla" (not Kolla Ansible)
Eric
*From:* Eric K. Miller *Sent:* Thursday, October 17, 2019 1:18 AM *To:* 'Radosław Piliszek' *Cc:* Michael Johnson; openstack-discuss *Subject:* RE: [Octavia][Kolla] Amphora build issues
Hi Radek,
In case this was useful, Kolla Ansible pulls the files (when using the "source" option) from:
http://tarballs.openstack.org/octavia/
So, I just adjusted the version it pulled for Octavia.
Eric
*From:* Radosław Piliszek [mailto:radoslaw.piliszek@gmail.com] *Sent:* Thursday, October 17, 2019 1:15 AM *To:* Eric K. Miller *Cc:* Michael Johnson; openstack-discuss *Subject:* Re: [Octavia][Kolla] Amphora build issues
Hi Eric,
Octavia has recently been bumped up to 4.1.0 [1]
This applies to the cases when you are either using our (upstream, in-registry) images or kolla from git.
Released kolla is behind.
@kolla
Stable branches are really stable so I am not sure whether we should not just point people willing to build their own images to use the version from git rather than PyPI, especially since our images are built from branch, not release.
[1] https://review.opendev.org/688426
Kind regards,
Radek
czw., 17 paź 2019 o 07:23 Eric K. Miller <emiller@genesishosting.com> napisał(a):
Success!
The current Kolla Ansible release simply has the 4.0.1 version specified in kolla-build.conf, which can be easily updated to 4.1.0.
So, I adjusted the kolla-build.conf file, re-built the Octavia containers, deleted the containers from the controllers, re-deployed Octavia with Kolla Ansible, and tested load balancer creation, and everything succeeded.
Again, much appreciated for the assistance.
Eric
-----Original Message----- From: Michael Johnson [mailto:johnsomor@gmail.com] Sent: Wednesday, October 16, 2019 5:36 PM To: Eric K. Miller Cc: openstack-discuss Subject: Re: [Octavia] Amphora build issues
This is caused by the controller version being older than the image version. Our upgrade strategy requires the control plane be updated before the image. A few lines above in the log you will see it is attempting to connect to /0.5 and not finding it.
You have two options: 1. update the controllers to use the latest stable/stein verison 2. build a new image, but limit it to an older version of stein (such as commit 15358a71e4aeffee8a3283ed08137e3b6daab52e)
We would recommend you run the latest minor release of stable/stein. (4.1.0 is the latest) https://releases.openstack.org/stein/index.html#octavia
I'm not sure why kolla would install an old release. I'm not very familiar with it.
Michael
On Wed, Oct 16, 2019 at 2:43 PM Eric K. Miller <emiller@genesishosting.com> wrote:
Looking at the error, it appears it can't find the exceptions.py
script, but it appears to be in the octavia worker container:
2019-10-16 16:27:49.416 23 ERROR oslo_messaging.rpc.server
WrappedFailure: WrappedFailure: [Failure: octavia.amphorae.drivers.haproxy.exceptions.NotFound: Not Found, Failure: octavia.amphorae.drivers.haproxy.exceptions.NotFound: Not Found]
(octavia-worker)[root@controller001 haproxy]# cd
/var/lib/kolla/venv/lib/python2.7/site- packages/octavia/amphorae/drivers/haproxy
(octavia-worker)[root@controller001 haproxy]# ls -al total 84 drwxr-xr-x. 2 root root 186 Sep 29 08:12 . drwxr-xr-x. 6 root root 156 Sep 29 08:12 .. -rw-r--r--. 1 root root 3400 Sep 29 08:12 data_models.py -rw-r--r--. 1 root root 4797 Sep 29 08:12 data_models.pyc -rw-r--r--. 1 root root 2298 Sep 29 08:12 exceptions.py -rw-r--r--. 1 root root 3326 Sep 29 08:12 exceptions.pyc -rw-r--r--. 1 root root 572 Sep 29 08:12 __init__.py -rw-r--r--. 1 root root 163 Sep 29 08:12 __init__.pyc -rw-r--r--. 1 root root 26572 Sep 29 08:12 rest_api_driver.py -rw-r--r--. 1 root root 25269 Sep 29 08:12 rest_api_driver.pyc
Eric