Skip to content

troubleshooting.md

Latest commit

 

History

History
41 lines (34 loc) · 1.63 KB

troubleshooting.md

File metadata and controls

41 lines (34 loc) · 1.63 KB

Troubleshooting

Verifying the operator deployment

  • check existence and status of the Performance Operator Deployment
    $ oc get deployment -A | grep performance-addon

  • if it doesn't exist, continue below with the CSV

  • check existence and status of the Performance Operator Pod
    $ oc get pod -A | grep performance-addon

  • check logs of the Performance Operator Pod
    $ oc logs -n ...

  • check existence and status of the Performance Operator Subscription
    $ oc get subscription -A | grep performance-addon

  • check existence and status of the Performance Operator CSV
    $ oc get csv -A | grep performance-addon

  • check existence and status of the Performance Operator CatalogSource
    $ oc get catalogsource -A | grep performance-addon

  • check general status of the cluster (failed or pending pods)
    $ oc get pod -A | grep -vE "Running|Completed"

Debugging performance tuning

  • check existence and status of the PerformanceProfile
    $ oc get performanceprofile
  • check logs of the Performance Operator Pod
    $ oc logs -n ...
  • check MachineConfigs, MachineConfigPools and Nodes
    $ oc get mc,mcp,nodes -o=wide
  • check machine config damons of the relevant nodes
    $ oc get pod -A -o=wide | grep machine-config-daemon
    $ oc logs -n ...
  • check tuned damons of the relevant nodes
    $ oc get pod -A -o=wide | grep tuned
    $ oc logs -n ...
  • check logs of cluster-node-tuning-operator Pod
    $ oc logs -n ...

Configuration hotfixes

In case a performance configuration needs to be amended please refer to configuration hotfixes.