Troubleshooting CNC Console

Not able to display the release version of the NF at CNCC banner

Problem: CNCC banner displays the release version of CNCC. But not displaying the release version of the NF.

Solution:

Both “About” section and Application name displayed next to Oracle logo use the envSystemName and envNFVersion helm fields.
The value set of envSystemName and envNFVersion combines to display the Application name (Application name = envSystemName + envNFVersion).
CNCC Core Custom values has envSystemName and envNFVersion mentioned in it, but these values can be overridden.

Unable to reach CNCC Core IP/port directly

Problem:Unable to reach CNCC Core IP/port directly. redirect_uri is inserted instead of directly accessing the CNCC Core.

Solution:

As per design, CNCC redirects requests to CNCC IAM for authentication. On successful authentication, CNCC IAM redirects the user back to CNCC GUI.

'Admin' user created under Cncc realm is unable to access CNCC IAM

Problem: Once a user created under Cncc realm is assigned an ‘Admin’ privilege, whether the user have the access to CNCC IAM.

Solution:

The users created under Cncc realm have access only to CNCC Core; not to CNCC IAM.
If a new admin user needs to be created who can login to CNCC IAM, that user has to be created under Master realm.

CNCC returns 403 error during NF Configuration

Problem: CNCConsole returns a 403 Error Code and error "Forbidden. Data could not be saved".

Error Code/Error Message:

403/Forbidden

Solution:

For doing the write operation on any NF via CNCConsole, user must have <NF>_WRITE role (permission).
User must login to CNCC IAM to check and assign the roles.
Check the roles of the user through which you have logged in, user must have both <NF>_READ and <NF>_WRITE roles assigned.

CNCConsole returns 500 - Internal Server Error

Problem: CNCConsole returns a 500 Error Code while accessing NF Resource.

Error Code/Error Message:

500/Internal Server Error

Solution:

This issue occurs when the NF routes are not configured correctly.
Ensure that correct routes for each NF are configured during deployment.

CNCC IAM is accessible but CNC Core is not accessible

Problem: CNCC IAM is accessible but CNCC Core is not accessible.

Error Message:

The ID Token contains invalid claims. (This is a JWT validation error, usually this indicates that the system clock on your server Is off.)

Solution:

In this case IAM (node1) was ahead of time and Ingress Gateway (node2) was 5 minutes behind.
When Ingress Gateway receives the token it was of future time, so it invalidates it by throwing "The ID Token contains invalid claims: {iat=2020-05-26T08:32:12Z}".
This issue occurs when Ingress Gateway is behind time and CNCC IAM is ahead of time.
It is important to have the same time in CNCC IAM and Ingress Gateway.
The key is to have the same time in both IAM and Ingress Gateway, in case they are running in different instances having a NTP server this issue will not happen, and in case both of them are deployed in the same instance neither.

The dependency issue of CNCC Core Routes id field name and service name

Problem:

The - id: scpc-configuration under route is mentioned as - id: scpc_configuration (with an underscore instead of a hyphen) and its not matching service name.

Solution:

id field in routes is used to uniquely identify the route, it can be any string. There is no dependency with service name.
- id: scpc-configuration or - id: scpc_configuration should not make any difference , it can be named as per convenience.

CNCC IAM admin password configured via kubectl secret is not reflected (Example: if configured cncc-iam-secret)

Problem:

CNCC IAM admin password change through cncc-iam-secret not working.

Solution:

During first time installation with fresh database, CNCC IAM reads password from cncc-iam-secret and stores it in database. So any updates to the admin password must be done via CNCC IAM GUI.

CNCC Debugging through Logs

For information about logs, refer the CNCC Logs section in the CNC Console User's Guide.

FAQ

Does CNCC support Command Line Interface (CLI) ?

Problem: Can NF APIs integrated with CNCC be accessed through curl/postman ?

Solution

NF configuration APIs can be accessed via CNCC GUI or directly using postman/curl.
CNCC enforces authentication and authorization in both the flows.
Steps are documented in Cloud Native Core Console User's Guide. about how to access APIs using postman/curl.