octavia/octavia/controller/worker/flows
Adam Harwell 96cce3ed74 Fix amp failover where failover already failed
If a failover ran on an amphora and was unsuccessful and reverted, it
would mark the amp status "DELETED" and un-busy the health record.
It would then be picked up on the next failover check, start failing
over, and break early since it appeared to be "unallocated".

Also, housekeeping can now clean up expired amphora records based on the
amphora's updated_at time instead of the health record's time, which
means the records won't be immediately cleaned up anymore after they go
through failover flows.

Change-Id: I848b7fc69b977fcb39f8a07e2ea5fc7bd37b5c7a
2018-06-05 14:10:00 -07:00
..
__init__.py Add license for empty __init__.py 2018-03-14 07:02:56 +09:00
amphora_flows.py Fix amp failover where failover already failed 2018-06-05 14:10:00 -07:00
health_monitor_flows.py Fix member operating status when add/remove HM 2017-11-09 15:09:19 -08:00
l7policy_flows.py The MarkL7PolicyActiveInDB is not necessary when l7policy deleted 2018-03-27 04:51:58 +00:00
l7rule_flows.py Fix inappropriate provisioning_status of l7 policy 2017-09-14 23:57:54 +12:00
listener_flows.py Handle missing security groups on listener delete 2018-01-30 09:55:33 -08:00
load_balancer_flows.py Deallocate the VIP prior to deleting the amphorae 2018-02-06 15:52:39 -08:00
member_flows.py Slightly reorder member flows 2018-05-09 11:17:58 -07:00
pool_flows.py Add cascade delete for APIv2 2017-05-08 13:39:00 -07:00