Hi Yvain, From the request Input to OOF i could see the TN_BH subnetCapabilities are missing, is there any issue while fetching those or NST is not composed of TN BH NSST? pl refer the below wiki for

#slicing #guilin #so

Invested further and found that the agent.sh script is not able to find a key 'cadi_alias' in the file /opt/app/osaaf/local/org.onap.so.cred.props and failing there. Understood that this file would be

#aaf #so

Hi Everyone, Getting below authentication error while trying to access the api/nslcm/v1/ns_instances for CreateNsRequest request in SO module. { "timestamp": "2021-05-10T13:14:46.443+00:00", "status":

#so #api

Hi, Could you make sure that your TRUSTSTORE property is pointing directly to the file and not to the folder. The file must also be mounted on the pod. Additionally, could you provide a copy of the ov

#install #honolulu #so

Hello Krzysztof, Thanks it worked for so-monitoring. Regarding camunda bpmn app/cockpit/default I ended up discovering the username and password (mso_admin and password1$). Thanks & Best, Paulo

#guilin #so

Hi all! In the Guilin release, instantiation via the NBI interface does not work for us: {{url-nbi}}/nbi/api/v4/serviceOrder - after a long wait, it gives an error: "Service Orchestrator Service Insta

#so #nbi

The error log when the latest-guilin.yaml is applied: 2021-01-08 07:43:36.190 ERROR 1 --- [ask-scheduler-8] o.o.d.a.w.http.EelfAuditLogInterceptor : Request Id: 0c589641-2289-4fb8-bba0-67c129b35d22, T

#vfc #policy #so

Might want to check with the SO team but I think I have seen this behavior when openstack is slow to do the instantiate for stack status. The default timers in SO will then trigger the re-submit logic

#so

Hi Emin, Thank you very much. I have checked this issue and the reason maybe that Modeling/etsicatalog uses readinessCheck component provided by OOM by: {{ include "common.readinessCheck.waitFor" (dic

#frankfurt #aai #so #sdc #guilin

If you still facing with this problem, the easiest way to check what is going on with the app is to try to run your app in your IDE. You only need to reconfigure override.yaml to point on one from oom

#so #vid

It seems to be possible to enable MultiCloud within the SO ServiceInstances call. (see https://docs.onap.org/projects/onap-integration/en/latest/docs_vfwHPA.html#docs-vfw-hpa). The option looks like:

#so #multicloud

For anyone else interested in making use of SO-Monitoring, We followed the steps below in order to resolve the issues getting SO-Monitoring running. Thank you @andreas-geissler@... for testing

#so

Also – does your openstack.rc indicate 5000 as the port that openstack is listening on ? I assume so or otherwise robot would have thrown an error but just checking. Brian

#so

Hi, try to go to oom/kubernetes/robot folder and run the following command: ./ete-k8s.sh <namespace> cloudconfigv3 and re-check the SO tables. You will find an additional entry for keystone_three. Ani

#so

Hi, …and last night’s deployment was even more broken; SO bpmn was full of database errors, and the gist of them was Caused by: java.sql.SQLException: CREATE command denied to user 'so_user'@'10-42-3-

#so #frankfurt

Hello, I am working on a BPMN process with Script Tasks where i want to call an external groovy file using the "External Resource". In the Script Task: "Pre Process Incoming Request" i have config the

#question #so #deployment

#SO Team (UTC) When: Wednesday, 27 November 2019 1:30pm to 2:30pm (UTC+00:00) UTC Repeats: Weekly on Wednesday, through Tuesday, 5 May 2020 Where: https://zoom.us/j/794508490 Organizer: Seshu Kumar se

#so #cal-invite

Reminder: #SO Team (UTC) When: Wednesday, 29 April 2020, 1:30pm to 2:30pm, (GMT+00:00) UTC Where:https://zoom.us/j/794508490 View Event Organizer: Seshu Kumar seshu.kumar.m@... Private Bridge D

#so #cal-reminder

Dear all, I would like to use Openstack as VIM with SSL enabled authentication. Openstack environement related files in the charts do not include SSL option. If there is no option to refer the SSL cer

#so

Dear SO experts, In the Frankfurt the authorization in the so-monitoring GUI is mandatory. By default, no users are created to access the so-monitoring GUI. Like was mentioned in mail https://lists.on

#so #portal