diff options
| author | varac <varacanero@zeromail.org> | 2014-06-11 10:23:48 +0200 |
|---|---|---|
| committer | varac <varacanero@zeromail.org> | 2014-06-11 10:23:48 +0200 |
| commit | dfa5bc15c9a866b3dad595ba9965539cbd229c93 (patch) | |
| tree | 1d5aa97e3905128e73acb02d22c12d1edfe78894 /docs/platform/known-issues.md | |
| parent | 364db6ffafd036ed768b126b53ad7909e066e152 (diff) | |
| parent | 4c3543f175252fae9ae48ac8f6accca207eeed8d (diff) | |
Merge branch 'master' of ssh://code.leap.se/leap_doc
Diffstat (limited to 'docs/platform/known-issues.md')
| -rw-r--r-- | docs/platform/known-issues.md | 7 |
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/platform/known-issues.md b/docs/platform/known-issues.md index 46a77de..5bf41a6 100644 --- a/docs/platform/known-issues.md +++ b/docs/platform/known-issues.md @@ -5,6 +5,13 @@ Here you can find documentation about known issues and potential work-arounds in the current Leap Platform release. +0.5.1 +===== +CouchDB Sync +------------ +You can't deploy new couchdb nodes after one or more have been deployed. Make *sure* that you configure and deploy all your couchdb nodes when starting the provider. The problem is that we dont not have a clean way of adding couch nodes after initial creation of the databases, so any nodes added after result in improperly synchronized data. See Bug [#5601](https://leap.se/code/issues/5601) for more information. + + 0.5.0rc1 ======== |