diff options
author | Taka Cho <takamune.cho@att.com> | 2019-01-30 21:12:53 -0500 |
---|---|---|
committer | Taka Cho <takamune.cho@att.com> | 2019-01-31 12:00:57 -0500 |
commit | 04730bef6af04017845163f8d42d8cb39bb81546 (patch) | |
tree | 556d28b93bd3cc7ccf24082e87155dd43054bf60 | |
parent | 0b07f027a26228dd080f2ad6fcfcc3dba4f4421e (diff) |
add one note in release note
A note is added for R3 Mtn release
Change-Id: I54618da5dd7b9219acbbda8fe47c48db745791b8
Issue-ID: APPC-1375
Signed-off-by: Taka Cho <takamune.cho@att.com>
-rw-r--r-- | docs/release-notes.rst | 4 |
1 files changed, 3 insertions, 1 deletions
diff --git a/docs/release-notes.rst b/docs/release-notes.rst index cb41f6887..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 -------------- @@ -178,7 +181,6 @@ Quick Links: - OpenStack Hypervisorcheck is turned off by default. - - OpenStack Hypervisorcheck is turned off by default. - Integration with MultiCloud is supported for Standalone Restart (i.e., not via DGOrchestrator). For any other action, such as Stop, Start, etc.. via MultiCloud requires the MultiCloud identity URL to be either passed in the payload or defined in appc.properties. |