Octavia loadbalancer are staying in OFFLINE
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
New
|
Undecided
|
Unassigned |
Bug Description
We have discovered that after some times the health-manager is not updating the operating-status of the loadbalancer.
We are running Octavia in Zed with Python 3.10 and a venv with those python library :
https:/
After a while, we won't see any logs like :
2023-08-22 17:02:40.672 6 DEBUG octavia.
and when we do a GMR on the process 6 we have :
https:/
/var/lib/
`LOG.
/usr/lib/
`self.
/usr/lib/
`self.
/usr/lib/
`self.
/usr/lib/
`self.
/usr/lib/
`self.
/usr/lib/
`hdlr.
/usr/lib/
`self.
/usr/lib/
`self.
/var/lib/
`eventlet.
/var/lib/
`return hub.switch()`
/var/lib/
`return self.greenlet.
But i don't think the health-manager is using eventlet
([O345] Usage of Python eventlet module not allowed --> https:/
And we are using oslo.log in 5.0.2 which include this patch : https:/
The conf we use :
https:/
If you have any idea don't hesitate
Hi,
it seems that olso.log 5.0.2 (and 5.0.1) was blocked in the requirements on master because of similar issues:
https:/ /review. opendev. org/c/openstack /requirements/ +/864573
there's a related launchpad issue in neutron: /bugs.launchpad .net/neutron/ +bug/1995091
https:/
it's not really clear in the report but it appears that, in one of their testing patches, they tried to comment out the LOG.<method> calls
our CI jobs still use (see https:/ /6df0d90b08f380 24b3b0- ddacc1cdacca358 2cad1fbbc53a5ba be.ssl. cf2.rackcdn. com/892285/ 1/check/ octavia- v2-dsvm- scenario- amphora- v2/beaa8d0/ controller/ logs/pip3- freeze. txt)
eventlet==0.33.1
oslo.log==5.0.0