summaryrefslogtreecommitdiff
path: root/CHANGES.md
diff options
context:
space:
mode:
authorelijah <elijah@riseup.net>2016-09-06 12:34:48 -0700
committerelijah <elijah@riseup.net>2016-09-06 12:35:24 -0700
commit26afb64224872777dd8739bf98ae04bad9a0e405 (patch)
tree4b529789edc8b3345471f608cce4ca6ae6ee3067 /CHANGES.md
parent90e4bca777f6edfbde29b590313cf938f75c53a7 (diff)
Added known issues to CHANGES.md
Diffstat (limited to 'CHANGES.md')
-rw-r--r--CHANGES.md11
1 files changed, 10 insertions, 1 deletions
diff --git a/CHANGES.md b/CHANGES.md
index f5332ca9..3fbb3ee1 100644
--- a/CHANGES.md
+++ b/CHANGES.md
@@ -27,7 +27,8 @@ You will need the new version of leap_cli:
workstation$ sudo gem install leap_cli --version=1.9
-Because 0.9 does not use submodules anymore, you must remove them before pulling the latest leap_platform from git:
+Because 0.9 does not use submodules anymore, you must remove them before pulling
+the latest leap_platform from git:
cd leap_platform
for dir in $(git submodule | awk '{print $2}'); do
@@ -39,6 +40,14 @@ Alternately, just clone a fresh leap_platform:
git clone https://leap.se/git/leap_platform
+Known Issues:
+
+* When upgrading, sometimes systemd does not report the correct state of a
+ daemon. The daemon will be not running, but systemd thinks it is. The symptom
+ of this is that a deploy will succeed but `leap test` will fail. To fix, you
+ can run `systemctl stop DAEMON` and then `systemctl start DAEMON` on the
+ affected host (systemctl restart seems to work less reliably).
+
Includes:
* leap_web: 0.8