summaryrefslogtreecommitdiff
path: root/releasenotes
diff options
context:
space:
mode:
authorZuul <zuul@review.openstack.org>2018-02-20 19:13:07 +0000
committerGerrit Code Review <review@openstack.org>2018-02-20 19:13:08 +0000
commit2a6a905949cd456667eaec6fb1cf5f09d03a97e2 (patch)
tree3de17196e376678104879579bbcff9ccadae374f /releasenotes
parent499979df5f33315259e74a2d38491b2d4a6282cd (diff)
parentd3352ff422db6ba6a5e7bd4f7220af0d97efd0ac (diff)
downloadkeystonemiddleware-2a6a905949cd456667eaec6fb1cf5f09d03a97e2.tar.gz
Merge "Identify the keystone service when raising 503"
Diffstat (limited to 'releasenotes')
-rw-r--r--releasenotes/notes/bug-1747655-6e563d9317bb0f13.yaml9
1 files changed, 9 insertions, 0 deletions
diff --git a/releasenotes/notes/bug-1747655-6e563d9317bb0f13.yaml b/releasenotes/notes/bug-1747655-6e563d9317bb0f13.yaml
new file mode 100644
index 0000000..65f4c5a
--- /dev/null
+++ b/releasenotes/notes/bug-1747655-6e563d9317bb0f13.yaml
@@ -0,0 +1,9 @@
+---
+fixes:
+ - |
+ [`bug/1747655 <https://bugs.launchpad.net/keystonemiddleware/+bug/1747655>`_]
+ When keystone is temporarily unavailable, keystonemiddleware correctly
+ sends a 503 response to the HTTP client but was not identifying which
+ service was down, leading to confusion on whether it was keystone or the
+ service using keystonemiddleware that was unavailable. This change
+ identifies keystone in the error response.