Issue with Refreshing the PCF Ops Center
This section describes how to refresh the PCF Ops Center to display the latest configurations.
Problem
The PCF Ops Center is not considering the recent configurations due to which you may observe stale data or not get the expected response.
Resolution
You can refresh the PCF Ops Center using the basic and advanced steps. Perform the advanced steps only when the basic steps do not resolve the issue.
Basic
-
Run the following to undeploy PCF from the Ops Center:
system mode shutdown
-
Use the following to manually purge any pending deployments from the helm:
helm delete --purge helm_chart_name
-
From the master node, run the following to delete the configMaps from the namespace where PCF is installed:
kubectl delete cm config_map_name -n namespace
-
Run the following to delete the product-specific configMaps from the CNEE namespace.
-
Use the following to list the available configMaps:
kubectl get configmaps -n namespace
From the list, determine the configMap that you want to delete.
-
Run the following to delete the configMap:
Kubectl delete configmap configmap_name -n namespace
-
-
Use the following commands to reinstall the helm chart. Once the chart is installed, a new instance of the PCF Ops Center is available.
helm upgrade –install release name addR/chart_name -f filenames --namespace namespace
Advanced
-
Remove the cnee-ops-center.
-
Delete the configMaps from the namespace.
For more information on step 1 and 2, see the Basic steps.
-
Install the PCF Ops Center. For information on how to PCF Ops Center, see Deploying and Accessing PCF.
The recent configuration is not rendered because the responsible pods are not in a healthy state to process the refresh request. To investigate the issue at the pod level, review the pod's state.
Use the following command to view the pod's logs:
kubectl describe pod pod_name -n namespace
Alternatively, you can review the consolidated set of logs, using the following command:
kubectl logs -n namespace consolidated-logging-0
For information about the event logs, see Event Logs.
In the logs, the values in the Status and Ready columns indicate the following:
-
If the Status column displays the state as Running, and the Ready column has the same number of containers on both sides of the forward-slash (/), then the pod is healthy and operational. This implies that the issue is at the application level. To investigate the application issue, check the logs of all the containers residing within the pods to detect the issue. Or, log into the container and review the logs.
-
If the Status column displays the state as Pending, Waiting, or CrashLoopBackOff, then run the following to review the details such as the messages, reasons, and other relevant information:
kubectl describe pod pod_name -n namespace
-
If the Status is init or ContainerCreating, it signifies that the pod is in the process of starting up.
-
If the Status is Running, and in the Ready column the number of containers on both sides of forward-slash (/) are different, then the containers have issues.
Run the following to view the details:
kubectl describe pod pod_name -n namespace
When reviewing the details, if the Ready column has the value as false then it indicates that the corresponding container has issues. Review the associated logs to understand the issue.
-
If the Status and Ready columns, and logs of the container do not indicate any issue, then verify that the required ingress or the service that is required to reach the application is up and running.