From caf132f409bf9b819ef48c44509aea6e80cb1b10 Mon Sep 17 00:00:00 2001
From: Alex Kavanagh <alex@ajkavanagh.co.uk>
Date: Thu, 8 Aug 2019 15:10:35 +0100
Subject: [PATCH] Release notes around Series upgrade

- Bug: #1839021 - hacluster charm "Resource;
                  res_ks_haproxy not running"

Related-Bug: #1839021
Change-Id: I0bdd6fe0599843bc288bd5ed77add90dd4063ed6
---
 doc/source/1907.rst | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)

diff --git a/doc/source/1907.rst b/doc/source/1907.rst
index c932f2d7..8e47c8c0 100644
--- a/doc/source/1907.rst
+++ b/doc/source/1907.rst
@@ -248,6 +248,26 @@ stable charm revision.
 See the `charm deployment guide <https://docs.openstack.org/project-deploy-guide/charm-deployment-guide/latest/app-upgrade-openstack.html>`__
 for more details.
 
+Series Upgrade Issues
+=====================
+
+Bug: #1839021: hacluster charm "Resource; res_ks_haproxy not running"
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+For an HA deployment, when performing a Trusty to Xenial upgrade, it's
+possible, if the keystone unit takes a long time to reboot and restart its
+service, that keystone's hacluster crm monitor may exhaust its retries and
+show a ``blocked`` state with the status message ``Resource: res_ks_haproxy not
+running``.
+
+In this case, running the following against the affected hacluster unit should
+resolve the issue once the associated keystone unit has completed its upgrade:
+
+.. code:: bash
+
+   juju run --unit <unit> sudo crm resource refresh
+
+where ``<unit>`` is (say) keystone/0.
 
 Deprecation Notices
 ===================