From 96340768941cf94706e8cb0630598ce3b6c95760 Mon Sep 17 00:00:00 2001 From: Freddy Date: Thu, 5 Mar 2020 13:04:04 -0700 Subject: [PATCH] 1.7 upgrade note (#7397) The Session API in Consul 1.7.0 and 1.7.1 is incompatible with prior versions of Consul. This PR adds a note to our version-specific upgrade guide to guard against users upgrading before the fix in 1.7.2 is released. --- website/source/docs/upgrade-specific.html.md | 13 +++++++++++-- 1 file changed, 11 insertions(+), 2 deletions(-) diff --git a/website/source/docs/upgrade-specific.html.md b/website/source/docs/upgrade-specific.html.md index 6a1dda278..e1f16c132 100644 --- a/website/source/docs/upgrade-specific.html.md +++ b/website/source/docs/upgrade-specific.html.md @@ -17,8 +17,17 @@ upgrade flow. ## Consul 1.7.0 -Consul 1.7.0 contains two major changes that may impact upgrades: -[stricter JSON decoding](#stricter-json-decoding) and [modified DNS outputs](#dns-ptr-record-output) +Consul 1.7.0 contains three major changes that impact upgrades: +[stricter JSON decoding](#stricter-json-decoding), [modified DNS outputs](#dns-ptr-record-output), +and [backward-incompatible Session API changes](#session-api). + +### Session API +Consul 1.7.0 introduced a backwards incompatible change to the Session API. +Queries to view or renew sessions from agents on earlier versions will be rejected. +This impacts features and products including: Vault, the Enterprise snapshot agent, and locks. + +The issue occurs when clients are still running 1.6.4 or earlier but servers have been upgraded to 1.7.0 or 1.7.1. +For this reason, we recommend you upgrade directly to 1.7.2 when it is available as it will include a fix for this issue. ### Stricter JSON Decoding