1
0
mirror of https://github.com/openshift/openshift-docs.git synced 2026-02-05 12:46:18 +01:00
Files
openshift-docs/modules/investigating-why-windows-machine-compute-node.adoc
2022-10-21 13:19:18 +00:00

23 lines
814 B
Plaintext

// Module included in the following assemblies:
//
// * support/troubleshooting/troubleshooting-windows-container-workload-issues.adoc
[id="investigating-why-windows-machine-compute-node_{context}"]
= Investigating why Windows Machine does not become compute node
There are various reasons why a Windows Machine does not become a compute node. The best way to investigate this problem is to collect the Windows Machine Config Operator (WMCO) logs.
.Prerequisites
* You installed the Windows Machine Config Operator (WMCO) using Operator Lifecycle Manager (OLM).
* You have created a Windows compute machine set.
.Procedure
* Run the following command to collect the WMCO logs:
+
[source,terminal]
----
$ oc logs -f deployment/windows-machine-config-operator -n openshift-windows-machine-config-operator
----