openshift-ex-diagnostics man page

openshift ex diagnostics — Diagnose common cluster problems


openshift ex diagnostics [Options]


This utility helps troubleshoot and diagnose known problems. It runs diagnostics using a client and/or the state of a running master / node host.

openshift ex diagnostics

If run without flags, it will check for standard config files for client, master, and node, and if found, use them for diagnostics. You may also specify config files explicitly with flags, in which case you will receive an error if they are not found. For example:

openshift ex diagnostics --master-config=/etc/origin/master/master-config.yaml

· If master/node config files are not found and the --host flag is not present, host diagnostics are skipped.

· If the client has cluster-admin access, this access enables cluster diagnostics to run which regular users cannot.

· If a client config file is not found, client and cluster diagnostics are skipped.

Diagnostics may be individually run by passing diagnostic name as arguments.

openshift ex diagnostics <DiagnosticName>

The available diagnostic names are: AggregatedLogging, AnalyzeLogs, ClusterRegistry, ClusterRoleBindings, ClusterRoles, ClusterRouter, ConfigContexts, DiagnosticPod, EtcdWriteVolume, MasterConfigCheck, MasterNode, MetricsApiProxy, NetworkCheck, NodeConfigCheck, NodeDefinitions, RouteCertificateValidation, ServiceExternalIPs, UnitStatus.



Client context to use for cluster administrator


Path to the config file to use for CLI requests.


The name of the kubeconfig context to use

-l, --diaglevel=1

Level of diagnostic output: 4: Error, 3: Warn, 2: Notice, 1: Info, 0: Debug


If true, look for systemd and journald units even without master/node config


Image template for DiagnosticPod to use in creating a pod


If true, when expanding the image template, use latest version, not release version


Set the level of log output (0-10)


Set per module logging with file|pattern=LEVEL,...


Path to master config file (implies --host)


Path to store network diagnostic results in case of errors


Image to use for network diagnostic pod


Image to use for network diagnostic test pod


Serving port on the network diagnostic test pod


Protocol used to connect to network diagnostic test pod


Path to node config file (implies --host)


If true, may be set to prevent diagnostics making any changes via the API

Options Inherited from Parent Commands


DEPRECATED: The API version to use when talking to the server


Username to impersonate for the operation


Path to the file container Azure container registry configuration information.


Path to a cert. file for the certificate authority


Path to a client certificate file for TLS


Path to a client key file for TLS


The name of the kubeconfig cluster to use


The Google Cloud Platform Service Account JSON Key to use for authentication.


If true, the server's certificate will not be checked for validity. This will make your HTTPS connections insecure


Maximum number of seconds between log flushes


Require server version to match client version

-n, --namespace=""

If present, the namespace scope for this CLI request


The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don't timeout requests.


The address and port of the Kubernetes API server


Bearer token for authentication to the API server


The name of the kubeconfig user to use

See Also



June 2016, Ported from the Kubernetes man-doc generator

Referenced By


Openshift CLI User Manuals June 2016