If the shared storage validation fails during the initial VMware Cloud Director appliance configuration, the deployer displays error messages that you can use to remediate the issue.

Problem

During the VMware Cloud Director appliance deployment, the deployer displays an error message referring to the NFS share.

Cause

If you do not prepare the transfer server storage for the VMware Cloud Director, the NFS validation during deployment fails.

Solution

Version Error Action
10.2 /opt/vmware/vcloud-director/data/transfer/xyz is owned by an unknown user with UID 999; expected 1003 Verify the user ID configuration of the vcloud user on the NFS server. The vcloud user ID must be with the same value on the NFS server and the appliance.
10.2 /opt/vmware/vcloud-director/data/transfer/xyz is owned by an unknown user with GID 999; expected 1002 Verify the group ID configuration of the vcloud user on the NFS server. The vcloud user ID must be with the same value on the NFS server and the appliance.
10.2 Unable to touch file on transfershare Determine why the appliance cannot write on the mounted NFS share. To confirm why it is not writeable, try mounting the NFS share using another Linux machine.
10.2 Timeout encountered during /usr/bin/mount -t nfs 10.150.170.3:/data/transfer /opt/vmware/vcloud-director/data/nfs-test. Duration: 5 seconds Determine why this appliance cannot mount the specified NFS share within 5 seconds. To confirm if the NFS share cannot be mounted in a timely manner, try mounting it using another Linux machine. Alternatively, verify the NFS server export settings for this NFS share.
10.2 Error encountered during /usr/bin/mount -t nfs 10.150.170.3:/data/transfer /opt/vmware/vcloud-director/data/nfs-test Determine why this appliance cannot mount the specified NFS share . To confirm if the NFS share cannot be mounted, try mounting it using another Linux machine. Alternatively, verify the NFS server export settings for this NFS share.
10.2 Transfer share directory does not exist: /opt/vmware/vcloud-director/data/transfer The transfer share directory or mount point does not exist. Create that directory.
10.2 Unexpected permissions on file /opt/vmware/vcloud-director/data/transfer/xyz while performing operation: touch xyz. Expected: root root 644. Found: root, root, 600 Determine why the file owner, group, or permissions defer from the expected values after performing the specified operation on the NFS transfer share and correct the problem.
10.2 NFS server clock is out of sync with respect to the appliance clock. Time difference is: 3 minutes, 12 seconds Verify the time settings on the NFS server and appliance. If either or both are not accurate, set them to the correct time and ensure they are synchronized using NTP.
10.2 Unexpected permissions on file /opt/vmware/vcloud-director/data/transfer/xyz while performing operation: chmod xyz. Expected: root root 750. Found: root, root, 700 Determine why the file owner, group, or permissions defer from the expected values after performing the specified operation on the NFS transfer share and correct the problem.
10.2 Unexpected permissions on file /opt/vmware/vcloud-director/data/transfer/xyz while performing operation: chown xyz. Expected: root root 750. Found: root, root, 700 Determine why the file owner, group, or permissions defer from the expected values after performing the specified operation on the NFS transfer share and correct the problem.
10.2 and later Invalid or missing command arguments. usage: nfsValidate nfs_mount_string The JSON request body cannot be parsed. Provide a valid JSON request body.
10.2 and later Empty nfs_mount string The NFS mount string is not in the request body. Provide an NFS mount string argument.
10.2 and later Invalid nfs_mount string: nfs_mount_string_argument Change the NFS mount string to the valid format IP_address:path
10.2 and later Invalid cell type: cell_type_string The cell type must be primary, standby, or cell. If the OVF parameter is not equal to any of these values, verify the appliance configuration.
10.2 and later Prerequisite OS configuration was not completed The /opt/vmware/appliance/etc/os-configuration-completed file is missing from the appliance. Configure the operating system.
10.2 and later Cloud Director appliance system setup already complete. The /opt/vmware/appliance/etc/vcd-configuration-completed file was found on the appliance. The cloud directory setup is already complete, and you must not run this script.
10.2 and later The 10.150.170.3:/data/transfer/cells directory already exists. The primary appliance requires that this be removed. This directory must not exist on the primary appliance. The directory exists on the NFS server and you must remove it.
10.2 and later The 10.150.170.3:/data/transfer/appliance-nodes directory already exists. The primary appliance requires that this be removed. This directory must not exist on the primary appliance. The directory exists on the NFS server and you must remove it.
10.2 and later responses.properties file already exists on transfer share. The primary appliance requires that this be removed. On the primary appliance, the responses.properties files must not exist, and you must remove them.
10.2 and later responses.properties file does not exist on transfer share. This should already exist on a standby or cell appliance. On a standby or cell appliance, the responses.properties file must exist. The primary appliance might not be configured yet. You must configure the primary appliance before configuring additional cells.
10.2 and later nfsValidate can not be run while system setup is in progress. Wait for the system setup to complete before attempting to run nfsValidate.
10.2 and later Unable to create tmp directory for use by this script: /opt/vmware/vcloud-director/data/nfs-test Verify file system permissions to determine why this directory cannot be created.
10.2.1 Unable to create file on provided NFS share. It may not be writeable. This may be due to the exported NFS filesystem being read-only or no_root_squash was not specified Determine why the appliance cannot write on the mounted NFS share. To confirm why it is not writeable, try mounting the NFS share using another Linux machine.
10.2.1 Unable to chmod file on provided transfershare Determine why the appliance cannot change the access permissions of file system objects on the mounted NFS share. Try mounting the NFS share using another Linux machine.
10.2.1 Unable to chown file on provided transfershare Determine why the appliance cannot change the owner of file system objects on the mounted NFS share. Try mounting the NFS share using another Linux machine.
10.2.1 Timeout encountered during mount Determine why this appliance cannot mount the specified NFS share within 5 seconds. To confirm if the NFS share cannot be mounted in a timely manner, try mounting it using another Linux machine. Alternatively, verify the NFS server export settings for this NFS share.
10.2.1 Error encountered during mount Determine why this appliance cannot mount the specified NFS share . To confirm if the NFS share cannot be mounted, try mounting it using another Linux machine. Alternatively, verify the NFS server export settings for this NFS share.
10.2.1 Provided NFS share is owned by an unknown user with UID 123; expected rootProvided NFS share is owned by an unknown group with GID 456; expected root Determine why the expected file owner, group, or both defer from the expected values after performing the specified operation on the NFS transfer share and correct the problem.
10.2.1 Unexpected ownership and/or permissions on provided NFS share. Expected: root:root with mode: 750. Found: root:root with mode 777 Determine why some or all of the expected values for file owner, group, and mode are not as expected after performing the specified operation on the NFS transfer share. Correct the problem.
10.2.1 NFS server clock is out of sync with respect to the appliance clock. Time difference is: 1:55:14.603510 Verify the time settings on the NFS server and appliance. If either or both are not accurate, set them to the correct time and ensure they are synchronized using NTP.