f5349aca00
When reloading haproxy, check if a "<service> is not active, cannot reload." error is triggered by systemd, it means that haproxy crashed during the reload. When this error is detected, verify if haproxy has reloaded correctly (check the socket and its uptime). Related-Bug: #2054666 Change-Id: Ibadf6e529d53fb5a45b73af57243cee5a3f70d9b
8 lines
314 B
YAML
8 lines
314 B
YAML
---
|
|
fixes:
|
|
- |
|
|
Added a workaround that prevent the listener PUT API call from failing if
|
|
haproxy crashes during a reload. The amphora-agent ensures that in case of
|
|
crashes, haproxy is correctly restarted and ready to accept incoming
|
|
requests (see https://bugs.launchpad.net/octavia/+bug/2054666)
|