octavia/octavia/tests/unit/controller
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
..
healthmanager Create disabled members in haproxy 2018-05-14 10:31:06 -07:00
housekeeping Fix amp failover where failover already failed 2018-06-05 14:10:00 -07:00
queue Add license for empty __init__.py 2018-03-14 07:02:56 +09:00
worker Fix amp failover where failover already failed 2018-06-05 14:10:00 -07:00
__init__.py Add license for empty __init__.py 2018-03-14 07:02:56 +09:00