Harald Jensås 4cf0147e86 Exclude current conductor from offline_conductors ... In some cases the current conductor may have failed to updated the heartbeat timestamp due to failure of resource starvation. When this occurs the dbapi get_offline_conductors method will include the current conductor in its return value. In this scenario the conductor may end up forcefully remove node reservations or allocations from itself, triggering takeover which fail on-going operations. This change adds a wrapper to exclude the current conductor. The wrapper will log a warning to raise the issue. Related-Bug: #1970484 Stroy: 2010016 Task: 45204 Change-Id: I6a8f38934b475f792433be6f0882540b82ca26c1		2022-04-28 10:28:26 +02:00
..
__init__.py	Remove copyright from empty files	2014-01-07 21:05:01 +08:00
allocations.py	Trivial: comment why we don't check retired in allocations	2021-05-20 11:02:56 +02:00
base_manager.py	Automatically configure enabled_***_interfaces	2021-12-20 15:11:17 +01:00
cleaning.py	Shorten error messages in commonly used modules	2022-02-17 19:16:52 +01:00
deployments.py	Shorten error messages in commonly used modules	2022-02-17 19:16:52 +01:00
manager.py	Exclude current conductor from offline_conductors	2022-04-28 10:28:26 +02:00
notification_utils.py	Add node console notifications	2016-12-23 08:51:54 +00:00
periodics.py	node_periodics: encapsulate the interface class check	2021-10-12 11:30:38 +02:00
rpcapi.py	Add "none" RPC transport that disables the RPC bus	2021-12-07 09:33:04 +01:00
steps.py	Refactor driver_internal_info updates to methods	2021-12-03 14:49:33 +13:00
task_manager.py	Avoid RPC notify_conductor_resume_{deploy,clean} in agent_base	2021-12-06 12:38:04 +01:00
utils.py	Exclude current conductor from offline_conductors	2022-04-28 10:28:26 +02:00
verify.py	Follow up to Add support for verify steps	2021-10-07 20:48:45 +10:00