OpenShift Troubleshooting: Difference between revisions
Jump to navigation
Jump to search
No edit summary |
|||
| Line 25: | Line 25: | ||
oadm diagnostics MetricsApiProxy | oadm diagnostics MetricsApiProxy | ||
=Pod Troubleshooting= | |||
oc -n <project-name> get pods | |||
oc -n <project-name> describe po/<pod-name> | |||
... | |||
Status: Failed | |||
Reason: MatchNodeSelector | |||
Message: Pod Predicate MatchNodeSelector failed | |||
Revision as of 20:40, 30 July 2017
Internal
Overview
The general technique is to increase the logging level of various OpenShift master (api, controllers) and node processes as described here:
--loglevel=10 seems to work fine.
Then tail the journalctl log.
For the master controller process:
journalctl -u atomic-openshift-master-controllers -f
For the node process:
journalctl -u atomic-openshift-node -f
Metrics Troubleshooting
oadm diagnostics MetricsApiProxy
Pod Troubleshooting
oc -n <project-name> get pods
oc -n <project-name> describe po/<pod-name> ... Status: Failed Reason: MatchNodeSelector Message: Pod Predicate MatchNodeSelector failed