From 3129228e229df9fb7d535c14fd11698b81f0361a Mon Sep 17 00:00:00 2001 From: Euan Harris Date: Mon, 11 Nov 2019 09:29:09 -0800 Subject: [PATCH] interlock: Default update failure action is now rollback This behaviour changed in Interlock 2.3.0, which was backported to all active UCP versions. The change was tracked by ENGCORE-117. Signed-off-by: Euan Harris --- ee/ucp/interlock/config/index.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/ee/ucp/interlock/config/index.md b/ee/ucp/interlock/config/index.md index 0de5dcb61c..d4417b1ee1 100644 --- a/ee/ucp/interlock/config/index.md +++ b/ee/ucp/interlock/config/index.md @@ -38,15 +38,15 @@ service and save it to a file: ucp-interlock ``` -By default, the `ucp-interlock` service is configured to pause if you provide an -invalid configuration. The service will not restart without manual intervention. +By default, the `ucp-interlock` service is configured to roll back to +a previous stable configuration if you provide an invalid configuration. -If you want the service to automatically rollback to a previous stable -configuration, you can update it with the following command: +If you want the service to pause instead of rolling back, you can update +it with the following command: ```bash docker service update \ - --update-failure-action rollback \ + --update-failure-action pause \ ucp-interlock ```