Open Stack

Hi guys,

I'm finishing to work on my POC for Octavia and after solving few issues
with my configuration I'm close to get a properly working setup.
However, I'm facing a small but yet annoying bug with the health-manager
receiving amphora heartbeat UDP packet which it consider as not correct and
so drop it.

Here are the messages that can be found in logs:

*2018-10-23 13:53:21.844 25 WARNING
octavia.amphorae.backends.health_daemon.status_message [-] calculated hmac:
faf73e41a0f843b826ee581c3995b7f7e56b5e5a294fca0b84eda426766f8415 not equal
to msg hmac:
6137613337316432636365393832376431343337306537353066626130653261 dropping
packet*

Which come from this part of the HM Code:

https://docs.openstack.org/octavia/pike/_modules/octavia/amphorae/backends/health_daemon/status_message.html#get_payload

The annoying thing is that I don't get why the UDP packet is considered as
stale and how can I try to reproduce the payload which is send to the
HealthManager.
I'm willing to write a simple PY program to simulate the heartbeat payload
but I don't now what's exactly the message and I think I miss some
informations.

Both HealthManager and the Amphora do use the same heartbeat_key and both
can contact on the network as the initial Health-manager to Amphora 9443
connection is validated.

As an effect to this situation, my loadbalancer is stuck in PENDING_UPDATE
mode.

Do you have any idea on how can I handle such thing or if it's something
already seen out there for anyone else?

Kind regards,
G.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-operators/attachments/20181023/1afa4da8/attachment.html>