Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

Issues and Solutions

No.IssuesSolution
1.Portal UI doesn’t go up and so you cannot access SDC UI via Portal UI
  1. Go to https://<<sdc_ip>>:<<sdc_port>/ with Google Chrome Dev
  2. Open Inspect and go to  Application section
  3. On left column, open Cookies 
  4. Add the following cookie key/value
    USER_ID cs0008  for designer role
    USER_ID demo for admin role

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] 

The WA is described here [you need to create new categories via api rest, not via sdc gui ]: SDC-4144 - Getting issue details... STATUS

3.Usecase UI not working 
(502 HTTP response code)

[https://{{ip}}:30284/iui/usecaseui-ui/]

The issue is described here  USECASEUI-726 - Getting issue details... STATUS

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

SDNC -  instantiateRANSliceAllocate-CPS  DG 1.3.4

fails due to missing parameters in the context :

  • getNearRTRIC-cps-response.[' + $id1 + '].GNBCUCPFunction_length  for CUCP workflow

  • getNearRTRIC-cps-response.[' + $id1 + '].GNBCUUPFunction_length for CUUP

So the RAN instantation fails.


  • No labels