From 1d38fd0d35381efbeda6ca142d3431595da2a78d Mon Sep 17 00:00:00 2001 From: Zuul Date: Mon, 27 May 2019 03:01:47 +0000 Subject: [PATCH] Update git submodules * Update watcher from branch 'master' - Merge "Require nova_client.api_version >= 2.56" - Require nova_client.api_version >= 2.56 The [nova_client]/api_version defaults to 2.56 since change Idd6ebc94f81ad5d65256c80885f2addc1aaeaae1. There is compatibility code for that change but if 2.56 is not available watcher_non_live_migrate_instance will still fail if a destination host is used. Since 2.56 has been available since the Queens version of nova it should be reasonable to require at least that version of nova is running for using Watcher. This adds code which enforces the minimum version along with a release note and "watcher-status upgrade check" check method. Note that it's kind of weird for watcher to have a config option like nova_client.api_version since compute API microversions are per API request even though novaclient is constructed with the single configured version. It should really be something the client (watcher in this case) determines using version discovery and gracefully enables features if the required nova API version is available, but that's a bigger change. Change-Id: Id34938c7bb8a5ca934d997e52cac3b365414c006 --- watcher | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/watcher b/watcher index 3b9364d4c7..59306b9a47 160000 --- a/watcher +++ b/watcher @@ -1 +1 @@ -Subproject commit 3b9364d4c79e6eeb8e049b3cf061f38d1512d818 +Subproject commit 59306b9a47b97c88b2e723f16d23eaebc92b3e23