Verify that NUMA-aware scheduable nodes have the noderesourcetopologies CR applied to them. Run the following command:

Run the following command to check that the CRD is created succesfully: 

$ grep -r "succesfully"
modules/cnf-checking-numa-aware-scheduler-logs.adoc:.. Run the following command to check that the CRD is created succesfully:
modules/nodes-vsphere-machine-set-concept-static-ip.adoc:The machine controller updates the machine with a status of `IPAddressClaimed` to indicate that a static IP address has succesfully bound to the `IPAddressClaim` resource. The machine controller applies the same status to a machine with multiple `IPAddressClaim` resources that each contain a bound static IP address.The machine controller then creates a virtual machine and applies static IP addresses to any nodes listed in the `providerSpec` of a machine's configuration.
modules/verifying-cluster-install-oci.adoc:Verify that your cluster was installed and is running effectively on {oci-first}. To succesfully install a cluster and deploy it on {oci-first}, you must create specific {oci} infrastucture resources. Additionally, you must ensure that the Assisted Installer can access these {oci} infrastucture resources.
rest_api/console_apis/consolequickstart-console-openshift-io-v1.adoc:| success describes the succesfully passed task. 

$ grep -r "scheduable"
modules/cnf-troubleshooting-numa-aware-workloads.adoc:. Verify that NUMA-aware scheduable nodes have the `noderesourcetopologies` CR applied to them. Run the following command:
modules/cnf-troubleshooting-numa-aware-workloads.adoc:. Verify the NUMA zone granularity for all scheduable nodes by running the following command:
modules/multi-architecture-modify-machine-set-aws.adoc:. You can check that the nodes are ready and scheduable with the following command:
modules/multi-architecture-modify-machine-set-gcp.adoc:. You can check that the nodes are ready and scheduable with the following command:
modules/multi-architecture-modify-machine-set.adoc:. You can check that the nodes are ready and scheduable with the following command: 

4.12+

always

1. see the description