From 60bf606db48eb575ead7c10914cb893878bfec94 Mon Sep 17 00:00:00 2001
From: David Shrewsbury <shrewsbury.dave@gmail.com>
Date: Mon, 23 Jul 2018 17:06:53 -0400
Subject: [PATCH] Add upgrade release note about aborted node status

Change-Id: Iff97c70589ebc41f33d114f6fd978aea8219b6b1
---
 .../notes/aborted-node-status-3fd18d39cb468f8f.yaml       | 8 ++++++++
 1 file changed, 8 insertions(+)
 create mode 100644 releasenotes/notes/aborted-node-status-3fd18d39cb468f8f.yaml

diff --git a/releasenotes/notes/aborted-node-status-3fd18d39cb468f8f.yaml b/releasenotes/notes/aborted-node-status-3fd18d39cb468f8f.yaml
new file mode 100644
index 000000000..a7efd1adc
--- /dev/null
+++ b/releasenotes/notes/aborted-node-status-3fd18d39cb468f8f.yaml
@@ -0,0 +1,8 @@
+---
+upgrade:
+  - |
+    A new node status (ABORTED) is added to the ZooKeeper data model. It
+    is recommended that, during your nodepool upgrade, you shut down all
+    launcher processes before restarting any of them. Running multiple
+    launchers with mixed support of this new node status may cause
+    unexpected errors to be reported in the logs.