Issues and Solutions - OPTION 1
No. | Issues | Solution |
---|---|---|
1. | Portal UI doesn’t go up and so you cannot access SDC UI via Portal UI |
This hack can be possible since SDC UI authentication mode is cookie based. So the attacker can override the cookie to force its request. |
2. | 'Create new Service' from SDC UI [empty field form] | |
3. | Usecase UI not working (502 HTTP response code) [https://{{ip}}:30284/iui/usecaseui-ui/] | |
4. | uui-server cannot process task management request | Use the usecaseui image 4.0.3 |
5. | SDNC ran-slice.api module api not found | Need to add the following parameter to sdnc statefulset k8s file resource: - name: SDNR_NORTHBOUND
value: "true"
|
6. | SDNC cannot communicate with CPS | Chnage CPS and CPS-TBDMT IPs into ran-slice-api-dg.properties at /opt/onap/ccsdk/data/properties |
7. | SDNC - instantiateRANSliceAllocate-CPS DG 1.3.4 fails due to missing parameters in the context :
So the RAN instantation fails. | WA : Go to DG Builder , load the instantiateRANSliceAllocate-CPS dg and remove the link to CUUP, CUCP and DU . |
8. | 5G Core Deployment fails into kud | WA:kubectl -n onap exec onap-mariadb-galera-0 -it -- mysql -uroot -psecretpassword -D catalogdb select * from cloud_sites; insert into cloud_sites(ID, REGION_ID, IDENTITY_SERVICE_ID, CLOUD_VERSION, CLLI, ORCHESTRATOR) values("k8sregionfour", "k8sregionfour", "DEFAULT_KEYSTONE", "2.5", "clli2", "multicloud"); select * from cloud_sites; exit |
9. | Multiple Communication Service deployments fail | WA: After each communication service instantation , you need to remove all services instances[communication service, orchestration tasks, nsi, nssi] before make another instantation. |
Issues and Solutions - OPTION 2
No. | Issues | Solution |
---|---|---|
1. | OOF timeout before returning the result of the plan | |
2. | SO bpmn timeout, before OOF returning a valid plan |