1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-07 00:48:01 +01:00
Files
openshift-docs/modules/capi-troubleshooting.adoc
2023-10-30 10:13:25 -04:00

31 lines
1.4 KiB
Plaintext

// Module included in the following assemblies:
//
// * machine_management/capi-machine-management.adoc
:_mod-docs-content-type: REFERENCE
[id="capi-troubleshooting_{context}"]
= Troubleshooting clusters that use the Cluster API
Use the information in this section to understand and recover from issues you might encounter. Generally, troubleshooting steps for problems with the Cluster API are similar to those steps for problems with the Machine API.
The Cluster CAPI Operator and its operands are provisioned in the `openshift-cluster-api` namespace, whereas the Machine API uses the `openshift-machine-api` namespace. When using `oc` commands that reference a namespace, be sure to reference the correct one.
[id="ts-capi-cli_{context}"]
== CLI commands return Cluster API machines
For clusters that use the Cluster API, `oc` commands such as `oc get machine` return results for Cluster API machines. Because the letter `c` precedes the letter `m` alphabetically, Cluster API machines appear in the return before Machine API machines do.
* To list only Machine API machines, use the fully qualified name `machines.machine.openshift.io` when running the `oc get machine` command:
+
[source,terminal]
----
$ oc get machines.machine.openshift.io
----
* To list only Cluster API machines, use the fully qualified name `machines.cluster.x-k8s.io` when running the `oc get machine` command:
+
[source,terminal]
----
$ oc get machines.cluster.x-k8s.io
----