From 316274a9d3808b5fa9731114e171e357e9f21c87 Mon Sep 17 00:00:00 2001 From: Takashi Kajinami Date: Mon, 10 Jun 2024 17:36:06 +0900 Subject: [PATCH] Fix wrong option mentioned in release notes The [conductor] graceful_timeout option does not exist, and the [conductor] heartbeat_timeout option is actually used instead. Change-Id: I689fcf8c392eecbcf8ee12b2f67f78f9f22d17aa --- releasenotes/notes/accurate_alive-d2687bca802211a4.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/releasenotes/notes/accurate_alive-d2687bca802211a4.yaml b/releasenotes/notes/accurate_alive-d2687bca802211a4.yaml index 87ccaa25e8..233044b7f7 100644 --- a/releasenotes/notes/accurate_alive-d2687bca802211a4.yaml +++ b/releasenotes/notes/accurate_alive-d2687bca802211a4.yaml @@ -4,7 +4,7 @@ fixes: Previously the ``conductors`` ``online`` database column is not considered when displaying the "baremetal conductor list" ``Alive`` status. This means that when a conductor is stopped gracefully it will be shown as - (inaccurately) alive for the duration of ``[conductor]graceful_timeout``. + (inaccurately) alive for the duration of ``[conductor]heartbeat_timeout``. A conductor is now considered alive if ``online`` is true and there is a - recent enough heartbeat. \ No newline at end of file + recent enough heartbeat.