mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
75 lines
3.1 KiB
Plaintext
75 lines
3.1 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * installing/installing_vsphere/using-vsphere-problem-detector-operator.adoc
|
|
|
|
:_mod-docs-content-type: REFERENCE
|
|
[id="vsphere-problem-detector-config-checks_{context}"]
|
|
= Configuration checks run by the {operator-name}
|
|
|
|
The following tables identify the configuration checks that the {operator-name} runs. Some checks verify the configuration of the cluster. Other checks verify the configuration of each node in the cluster.
|
|
|
|
.Cluster configuration checks
|
|
[options="header",cols="20,80a"]
|
|
|===
|
|
|Name
|
|
|Description
|
|
|
|
|`CheckDefaultDatastore`
|
|
|Verifies that the default datastore name in the {vmw-full} configuration is short enough for use with dynamic provisioning.
|
|
|
|
If this check fails, you can expect the following:
|
|
|
|
* `systemd` logs errors to the journal such as `Failed to set up mount unit: Invalid argument`.
|
|
|
|
* `systemd` does not unmount volumes if the virtual machine shuts down or reboots without draining all the pods from the node.
|
|
|
|
If this check fails, reconfigure {vmw-short} with a shorter name for the default datastore.
|
|
|
|
|`CheckFolderPermissions`
|
|
|Verifies the permission to list volumes in the default datastore. You must enable the permission to create volumes. The Operator verifies the permission by listing the `/` and `/kubevols` directories. When the Operator performs the check, the root directory must exist. The `/kubevols` directory might not exist at the time of the check. The creation of the `/kubevols` directory occurs when the datastore supports dynamic provisioning.
|
|
|
|
If this check fails, review the required permissions for the vCenter account that you specified during the {product-title} installation.
|
|
|
|
|`CheckStorageClasses`
|
|
|Verifies the following:
|
|
|
|
* The fully qualified path to each persistent volume that the storage class provisions does not go lower than 255 characters.
|
|
|
|
* The storage class can use only one storage policy and the policy must be defined.
|
|
|
|
|`CheckTaskPermissions`
|
|
|Verifies the permission to list recent tasks and datastores.
|
|
|
|
|`ClusterInfo`
|
|
|Collects the cluster version and UUID from {vmw-short} vCenter.
|
|
|===
|
|
|
|
.Node configuration checks
|
|
[options="header",cols="20,80a"]
|
|
|===
|
|
|Name
|
|
|Description
|
|
|
|
|`CheckNodeDiskUUID`
|
|
|Verifies that all the {vmw-short} virtual machines include the `disk.enableUUID=TRUE` configuration.
|
|
|
|
If this check fails, see the link:https://access.redhat.com/solutions/4606201[How to check `disk.EnableUUID` parameter from VM in vSphere] Red Hat Knowledgebase solution.
|
|
|
|
|`CheckNodeProviderID`
|
|
|Verifies that all nodes have the `ProviderID` configuration from {vmw-short} vCenter. This check fails when the output from the following command does not include a provider ID for each node.
|
|
|
|
[source,terminal]
|
|
----
|
|
$ oc get nodes -o custom-columns=NAME:.metadata.name,PROVIDER_ID:.spec.providerID,UUID:.status.nodeInfo.systemUUID
|
|
----
|
|
|
|
If this check fails, reference the {vmw-short} product documentation on how to set the provider ID for each node in the cluster.
|
|
|
|
|`CollectNodeESXiVersion`
|
|
|Reports the version of the ESXi hosts that run nodes.
|
|
|
|
|`CollectNodeHWVersion`
|
|
|Reports the virtual machine hardware version for a node.
|
|
|===
|
|
|