-
Bug
-
Resolution: Done
-
Medium
-
Guilin Release
-
None
-
Weely Guilin Lab hosted in Orange DC
attached SDNC logs
onap-sdnc-0 2/2 Running 0 2d3h
onap-sdnc-ansible-server-856bcdb849-tfpds 1/1 Running 0 8d
onap-sdnc-db-0 1/1 Running 0 8d
onap-sdnc-dbinit-job-qr4g8 0/1 Completed 0 8d
onap-sdnc-dgbuilder-7f99ddd844-h95jg 1/1 Running 0 8d
onap-sdnc-dmaap-listener-7cd7d7ddb6-nppfr 1/1 Running 0 8d
onap-sdnc-sdnrdb-init-job-fphqf 0/1 Completed 0 8d
onap-sdnc-ueb-listener-ff996bb5b-tr8gb 1/1 Running 0 8d
onap-sdnc-web-798fd9dccb-cfvpd 1/1 Running 0 8d
onap-so-sdnc-adapter-6d844689b8-75ptw 2/2 Running 0 8dlogs of tests run after the installation: https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/11-30-2020_12-11/
Weely Guilin Lab hosted in Orange DC attached SDNC logs onap-sdnc-0 2/2 Running 0 2d3h onap-sdnc-ansible-server-856bcdb849-tfpds 1/1 Running 0 8d onap-sdnc-db-0 1/1 Running 0 8d onap-sdnc-dbinit-job-qr4g8 0/1 Completed 0 8d onap-sdnc-dgbuilder-7f99ddd844-h95jg 1/1 Running 0 8d onap-sdnc-dmaap-listener-7cd7d7ddb6-nppfr 1/1 Running 0 8d onap-sdnc-sdnrdb-init-job-fphqf 0/1 Completed 0 8d onap-sdnc-ueb-listener-ff996bb5b-tr8gb 1/1 Running 0 8d onap-sdnc-web-798fd9dccb-cfvpd 1/1 Running 0 8d onap-so-sdnc-adapter-6d844689b8-75ptw 2/2 Running 0 8d logs of tests run after the installation: https://logs.onap.org/onap-integration/weekly/onap_weekly_pod4_master/11-30-2020_12-11/ log-sdnc-pb.zip
During stability test, we trun the basic_vm continuously (when it finishes, we restart it)
During a 7 days tests, it was needed to restart the SDNC to recover the PASS state of the test.
We can see in the graph that the memory is increasing and when reaching a threshold, the test does not work anymore
it is documented in the test stability page
Note a simple restart of the SDNC fixes the issue.
The limits in OOM are set to 4 GiB
the requests to 2 GiB
even the limit is lower that the consumption recorded by prometheus. The request/limits are probably too low.