-
Story
-
Resolution: Done
-
Medium
-
None
Rancher ONAP OOM deployment do not deploy ONAP Portal properly. No startup or log activities in ONAP Portal shipped to Logstash because filebeat.yml log path and Portal Log paths are different. logs in portal - need to update logback.xml and pv in OOM.
Portal logs path in ONAP Portal container - /opt/apache-tomcat-8.0.37/logs/onapportal
Path in Portal filebeat.yml file- /var/log/onap
michaelobrien - portal-sdk will also need the fix
- blocks
-
LOG-488 LOG Pipeline Integrity: Docker to Filebeat /var/log/onap validation across all 2/2 components
- Closed
-
LOG-230 Pairwise integration testing - verify single log makes it through ELK into Kibana
- Closed
- is blocked by
-
LOG-486 Elasticsearch restart throws disk quota exceeded
- Closed
- relates to
-
LOG-481 ConfigMap is ReadOnly - The owner of elasticsearch.yml should be “elasticsearch” not root.
- Closed
- mentioned in
-
Page Loading...