Skip to content

Commit 8613c50

Browse files
Joao Fernandesjoaofnfernandes
Joao Fernandes
authored andcommitted
Release UCP 2.1.2
1 parent bd9d2bc commit 8613c50

File tree

3 files changed

+55
-2
lines changed

3 files changed

+55
-2
lines changed

_config.yml

+2-2
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ defaults:
9898
scope:
9999
path: "datacenter"
100100
values:
101-
ucp_latest_image: "docker/ucp:2.1.1"
101+
ucp_latest_image: "docker/ucp:2.1.2"
102102
dtr_latest_image: "docker/dtr:2.2.3"
103103
-
104104
scope:
@@ -127,7 +127,7 @@ defaults:
127127
values:
128128
ucp_version: "2.1"
129129
dtr_version: "2.2"
130-
docker_image: "docker/ucp:2.1.1"
130+
docker_image: "docker/ucp:2.1.2"
131131
-
132132
scope:
133133
path: "datacenter/ucp/2.0"

_data/ddc_offline_files.yaml

+2
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,8 @@
66

77
- ucp-version: "2.1"
88
tar-files:
9+
- description: "UCP 2.1.2"
10+
url: https://packages.docker.com/caas/ucp_images_2.1.2.tar.gz
911
- description: "UCP 2.1.1"
1012
url: https://packages.docker.com/caas/ucp_images_2.1.1.tar.gz
1113
- description: "UCP 2.1.0"

datacenter/ucp/2.1/guides/release-notes/index.md

+51
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,57 @@ You can then use [the upgrade instructions](../admin/upgrade.md), to
1313
upgrade your installation to the latest release.
1414

1515

16+
## Version 2.1.2
17+
18+
(29 Mar 2017)
19+
20+
**Known issues**
21+
22+
There is known issue in UCP 2.1 where upgrading from UCP 1.1.z can cause swarm
23+
to leave worker nodes in a pending state with the message:
24+
25+
```
26+
[Pending] Completing node registration
27+
```
28+
29+
There are two workarounds for rectifying this issue:
30+
31+
1. When upgrading from UCP 1.1.z, first upgrade to UCP 2.0.z, and then to UCP
32+
2.1.z. This will prevent the issue from happening, and is the recommended upgrade path.
33+
2. If you have already upgraded from UCP 1.1.z directly to UCP 2.1.z, you can
34+
fix the issue by restarting the ucp-swarm-manager container on each of your UCP
35+
controller nodes.
36+
37+
This issue will be fixed in UCP 2.1.3.
38+
39+
**Bug fixes**
40+
41+
* Core
42+
* `ucp-reconcile` service now correctly brings up `ucp-kv` container if it
43+
has stopped or become unreachable
44+
* Fixed known issue in which users are unable to log into UCP UI after upgrading
45+
from UCP 2.1.0 to 2.1.1 because the parameter for maximum concurrent users was
46+
incorrectly defaulted to '0'
47+
* Fixed an issue where the UCP manager becomes unresponsive and requires a restart
48+
if `docker ps` or `docker info` calls to engine take a long time for a response
49+
* HTTP Routing Mesh now correctly provides httplog for debug logging of services
50+
* `docker node ls -f` now correctly filters when run against a UCP cluster
51+
* `docker inspect task` no longer returns errors when run against a UCP cluster
52+
* UCP now correctly reports progress when loading an image from CLI
53+
54+
* docker/ucp image
55+
* UCP support dumps now include Docker Engine daemon logs
56+
* Host address IPs are now automatically added to SANs during install
57+
* UCP now reports its version number in the CLI after being installed
58+
59+
* UI/UX
60+
* Deploying Compose-based applications in the GUI now works correctly when
61+
Docker Content Trust "Run Only Signed Images" is turned on
62+
* Fixed an issue where UI temporarily showed more tasks for a service than
63+
actually existed
64+
* Fixed an issue in which metrics incorrectly displayed `0%` in the UI
65+
66+
1667
## Version 2.1.1
1768

1869
(14 Mar 2017)

0 commit comments

Comments
 (0)