From cbb215337709afd35dc89987cde65a8ea2c9d0d9 Mon Sep 17 00:00:00 2001 From: Julia Kreger Date: Tue, 5 Apr 2016 15:26:24 -0400 Subject: [PATCH] Follow-up to I244c3f31d0ad26194887cfb9b79f96b5111296c6 Addressed minor nits in release notes for the review noted above. Change-Id: I4e3afcb1c71e2d4ab407cd25bfcddd17ee895245 --- ...do-not-power-off-non-deploying-nodes-0a3aed7c8ea3940a.yaml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/releasenotes/notes/ilo-do-not-power-off-non-deploying-nodes-0a3aed7c8ea3940a.yaml b/releasenotes/notes/ilo-do-not-power-off-non-deploying-nodes-0a3aed7c8ea3940a.yaml index ed0dcd3cdc..fcd23a8f13 100644 --- a/releasenotes/notes/ilo-do-not-power-off-non-deploying-nodes-0a3aed7c8ea3940a.yaml +++ b/releasenotes/notes/ilo-do-not-power-off-non-deploying-nodes-0a3aed7c8ea3940a.yaml @@ -1,10 +1,10 @@ --- fixes: - - A bug was identified in the behavior of the ilo driver + - A bug was identified in the behavior of the iLO drivers where nodes that are not active but taking part of a conductor takeover could be powered off. In preparation for new features and functionality, that risk encountering this bug, we are limiting the deployment preparation steps to the ``deploying`` - state to prevent nodes from being erroniuosly + state to prevent nodes from being erroneously powered off.