octavia

History

ZhaoBo a166c89b64 [UDP] Fix failed member always in DRAIN status 1. Remove 'inhibit_on_failure' option from realserver configuration block. Then when the member is failed which means the MISC_CHECK is failed, the amp agent can not get the member info from kernel ip_vs file, and it will return status DOWN to health manger, then the member status will be ERROR, and its associated pool and loadbalancer will be in DEGRADED status. Alternative: Using notify_up/notify_down to write the status into a member specific file, then we can read the member status from that file directly. Change-Id: I940681b8109b05334ebb5befc58b43f08d2a1148 Story: 2003198 Task: 23354	2018-08-08 04:24:16 +00:00
..
__init__.py	UDP jinja template	2018-08-01 10:18:31 -07:00
test_lvs_jinja_cfg.py	[UDP] Fix failed member always in DRAIN status	2018-08-08 04:24:16 +00:00

ZhaoBo a166c89b64 [UDP] Fix failed member always in DRAIN status

1. Remove 'inhibit_on_failure' option from realserver configuration block.
   Then when the member is failed which means the MISC_CHECK is failed,
   the amp agent can not get the member info from kernel ip_vs file, and
   it will return status DOWN to health manger, then the member status
   will be ERROR, and its associated pool and loadbalancer will be in
   DEGRADED status.

Alternative:
Using notify_up/notify_down to write the status into a member specific
file, then we can read the member status from that file directly.

Change-Id: I940681b8109b05334ebb5befc58b43f08d2a1148
Story: 2003198
Task: 23354

2018-08-08 04:24:16 +00:00

__init__.py

UDP jinja template

2018-08-01 10:18:31 -07:00

test_lvs_jinja_cfg.py

[UDP] Fix failed member always in DRAIN status

2018-08-08 04:24:16 +00:00