Troubleshooting A1-Policy functions

After successful installation, control panel shows "No Type" as policy type as shown below.
If there is no policy type shown and UI looks like below, then the setup can be investigated with below steps (It could be due to synchronization delay as well, It gets fixed automatically after few minutes)
Verify the A1 PMS logs to make sure that the connection between A1 PMS and a1controller is successful.
- Command to check pms logs
  Kubernetes command to get PMS logs
  kubectl logs policymanagementservice-0 -n nonrtric
- Command to enable debug logs in PMS (Command below should be executed inside k8s pods or the host address needs to be updated with the relevant port forwarding)
  Enabling debug logs in PMS
  curl --request POST \ --url http://policymanagementservice:9080/actuator/loggers/org.onap.ccsdk.oran.a1policymanagementservice \ --header 'Content-Type: application/json' \ --data '{ "configuredLevel": "DEBUG" }'
Try removing the controller information in specific simulator configuration and verify the simulator are working without a1controller.
application_configuration.json
... { "name":"ric1", "baseUrl":"https://a1-sim-osc-0.a1-sim:8185", "managedElementIds":[ "kista_1", "kista_2" ] }, ...
For troubleshooting the curl command is available in the can be used in controlpanel pod.