From 51c40711d37003a740f11065bd9445a0dcfaef08 Mon Sep 17 00:00:00 2001 From: Manuel Giffels Date: Tue, 19 Apr 2022 16:58:51 +0200 Subject: [PATCH] Add changelog for #234 --- docs/source/changelog.rst | 1 + .../234.fixed_state_transition_for_stopped_workers.yaml | 9 +++++++++ 2 files changed, 10 insertions(+) create mode 100644 docs/source/changes/234.fixed_state_transition_for_stopped_workers.yaml diff --git a/docs/source/changelog.rst b/docs/source/changelog.rst index 07ff25f9..3c78395d 100644 --- a/docs/source/changelog.rst +++ b/docs/source/changelog.rst @@ -35,6 +35,7 @@ Fixed * Unique constraints in database schema have been fixed to allow same machine_type and remote_resource_uuid on multiple sites * Update the remote_resource_uuid in sqlite registry on a each update +* Fixed state transition for stopped workers [0.6.0] - 2021-08-09 ==================== diff --git a/docs/source/changes/234.fixed_state_transition_for_stopped_workers.yaml b/docs/source/changes/234.fixed_state_transition_for_stopped_workers.yaml new file mode 100644 index 00000000..c07714ee --- /dev/null +++ b/docs/source/changes/234.fixed_state_transition_for_stopped_workers.yaml @@ -0,0 +1,9 @@ +category: fixed +summary: "Fixed state transition for stopped workers" +description: | + Fixes an unexpected behaviour for Drones in AvailableState in case the HTCondor daemon on nodes is shutdown + automatically causing the machine status to be NotAvailable, while the resource status continues to be Running. In + that case the drone state is re-set to IntegratingState. Since HTCondor is not restarted, the Drone remains in this + state forever. +pull requests: + - 234