diff options
author | Taka Cho <takamune.cho@att.com> | 2019-01-30 21:08:59 -0500 |
---|---|---|
committer | Taka Cho <takamune.cho@att.com> | 2019-01-31 12:05:23 -0500 |
commit | a5af4b57b33907b68ecf313dec8a3b1013568466 (patch) | |
tree | 856300b8c7af2141232f3e6ee9b3caf4e2c6f457 /docs | |
parent | e374b2e5df39abeac50b587a9426ebc9bed25c26 (diff) |
add one note in release note
A note is added for R3 Mtn release
Change-Id: I58b435d279601cf90b951b12b7fdc2e2397676b1
Issue-ID: APPC-1375
Signed-off-by: Taka Cho <takamune.cho@att.com>
Diffstat (limited to 'docs')
-rw-r--r-- | docs/release-notes.rst | 3 |
1 files changed, 3 insertions, 0 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index 7cb420f4a..8b391800f 100644 --- a/docs/release-notes.rst +++ b/docs/release-notes.rst @@ -40,6 +40,9 @@ The Casablanca maintenance release fixed the following bugs: - `CCSDK-741 <https://jira.onap.org/browse/CCSDK-741>`_ - Removed Work-around required for vCPE use case to correct the error described in CCSDK ticket. +Special Note for `APPC-1367 <https://jira.onap.org/browse/APPC-1367>`_ - APPC fails healthcheck with 404 error: + + During testing, we found there is a timing issue. When using OOM to deploy to k8s environment the clustered MariaDB database is not accessible at the time when the APPC pod is trying to insert the DG into MariaDb. This would cause the healthcheck issue. The workaround to solve this issue is redeploying the APPC pod. Version: 1.4.3 -------------- |