If an Amphora never sends a heartbeat, it does NOT get deleted and created again
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
octavia |
Invalid
|
High
|
Unassigned |
Bug Description
Currently, when an Amphora comes online it should start sending heartbeats to the health manager. The health manager also spawns a process to check if any heart beats are stale by reading the heartbeat table (amphora_health). If it detects a stale heartbeat in that table, it'll initialize a delete and recreate of the stale amphora.
If an amphora is created but never sends a heartbeat, a record is never inserted into the amphora_health table, and thus the stale heartbeat check will never know that amphora is missing heartbeats.
A solution would be to insert a row into the amphora_health table right before the load balancer is marked ACTIVE. This could have timing issues though so perhaps a better solution can be figured out.
Also, this fix is dependent on this bug getting fixed:
https:/
AND it needs to keep in mind the solution to this bug:
Changed in octavia: | |
importance: | Undecided → High |
Changed in octavia: | |
assignee: | nobody → Trevor Vardeman (trevor-vardeman) |
tags: | added: target-mitaka |
tags: | removed: target-mitaka |
tags: | added: osic |
tags: | removed: osic |
Fix proposed to branch: master /review. openstack. org/271512
Review: https:/