Unable to read /tmp/suds

You might see an error in the /var/log/cinder/volume.log file after you deploy a VMware driver topology.

Problem

You might see the following error in the /var/log/cinder/volume.log file after you deploy a VMware driver topology.

'unable to read /tmp/suds'

When you try to manage the VMware compute nodes with OpenStack, the error appears in the /var/log/cinder/volume.log file on the controller node.

Cause

OpenStack uses the python-suds module to support SOAP communications (communicating to vSphere vCenter). The python-suds module creates /tmp/suds folder for caching the runtime files. The cached contents can be used by both Nova or Cinder. Therefore, the folder must have read and write permission for Nova and Cinder (for all users). If the user changes umask to 027, for example, when Nova or Cinder services start, the suds module creates the folder /tmp/suds with permission 750. This prevents other OpenStack services to write or read the contents from that folder and causes the permission error.

Resolution

There are two solutions to resolve the problem.

Set the system umask to 022 (which is the system default) before you deploy OpenStack.
Use the 'chmod a+rx -R /tmp/suds' command, if the /tmp/suds is already created.