From 8613c50dbe18feba7cfca3832a7b1378ee64203e Mon Sep 17 00:00:00 2001 From: Joao Fernandes Date: Thu, 30 Mar 2017 13:53:41 -0700 Subject: [PATCH] Release UCP 2.1.2 --- _config.yml | 4 +- _data/ddc_offline_files.yaml | 2 + .../ucp/2.1/guides/release-notes/index.md | 51 +++++++++++++++++++ 3 files changed, 55 insertions(+), 2 deletions(-) diff --git a/_config.yml b/_config.yml index ecb83ccd8f..8cbdd0e395 100644 --- a/_config.yml +++ b/_config.yml @@ -98,7 +98,7 @@ defaults: scope: path: "datacenter" values: - ucp_latest_image: "docker/ucp:2.1.1" + ucp_latest_image: "docker/ucp:2.1.2" dtr_latest_image: "docker/dtr:2.2.3" - scope: @@ -127,7 +127,7 @@ defaults: values: ucp_version: "2.1" dtr_version: "2.2" - docker_image: "docker/ucp:2.1.1" + docker_image: "docker/ucp:2.1.2" - scope: path: "datacenter/ucp/2.0" diff --git a/_data/ddc_offline_files.yaml b/_data/ddc_offline_files.yaml index 4bd898ea39..723e498fbf 100644 --- a/_data/ddc_offline_files.yaml +++ b/_data/ddc_offline_files.yaml @@ -6,6 +6,8 @@ - ucp-version: "2.1" tar-files: + - description: "UCP 2.1.2" + url: https://packages.docker.com/caas/ucp_images_2.1.2.tar.gz - description: "UCP 2.1.1" url: https://packages.docker.com/caas/ucp_images_2.1.1.tar.gz - description: "UCP 2.1.0" diff --git a/datacenter/ucp/2.1/guides/release-notes/index.md b/datacenter/ucp/2.1/guides/release-notes/index.md index e8807489f8..35a9f0735f 100644 --- a/datacenter/ucp/2.1/guides/release-notes/index.md +++ b/datacenter/ucp/2.1/guides/release-notes/index.md @@ -13,6 +13,57 @@ You can then use [the upgrade instructions](../admin/upgrade.md), to upgrade your installation to the latest release. +## Version 2.1.2 + +(29 Mar 2017) + +**Known issues** + +There is known issue in UCP 2.1 where upgrading from UCP 1.1.z can cause swarm +to leave worker nodes in a pending state with the message: + +``` +[Pending] Completing node registration +``` + +There are two workarounds for rectifying this issue: + +1. When upgrading from UCP 1.1.z, first upgrade to UCP 2.0.z, and then to UCP +2.1.z. This will prevent the issue from happening, and is the recommended upgrade path. +2. If you have already upgraded from UCP 1.1.z directly to UCP 2.1.z, you can +fix the issue by restarting the ucp-swarm-manager container on each of your UCP +controller nodes. + +This issue will be fixed in UCP 2.1.3. + +**Bug fixes** + +* Core + * `ucp-reconcile` service now correctly brings up `ucp-kv` container if it + has stopped or become unreachable + * Fixed known issue in which users are unable to log into UCP UI after upgrading + from UCP 2.1.0 to 2.1.1 because the parameter for maximum concurrent users was + incorrectly defaulted to '0' + * Fixed an issue where the UCP manager becomes unresponsive and requires a restart + if `docker ps` or `docker info` calls to engine take a long time for a response + * HTTP Routing Mesh now correctly provides httplog for debug logging of services + * `docker node ls -f` now correctly filters when run against a UCP cluster + * `docker inspect task` no longer returns errors when run against a UCP cluster + * UCP now correctly reports progress when loading an image from CLI + +* docker/ucp image + * UCP support dumps now include Docker Engine daemon logs + * Host address IPs are now automatically added to SANs during install + * UCP now reports its version number in the CLI after being installed + +* UI/UX + * Deploying Compose-based applications in the GUI now works correctly when + Docker Content Trust "Run Only Signed Images" is turned on + * Fixed an issue where UI temporarily showed more tasks for a service than + actually existed + * Fixed an issue in which metrics incorrectly displayed `0%` in the UI + + ## Version 2.1.1 (14 Mar 2017)