Why does RHEV-M fail to mount NetApp NFS?

Solution In Progress - Updated -

Issue

In order for RHEV to attach and initialize any NFS storage (including NetApp NFS), it has to own the filesystem. By default, the user and group ownership of a given NFS export is “root”. RHEV-M is not currently able to mount the NFS export, then change the ownership on it’s own. Additionally, the default permissions in Clustered ONTAP are “700”, which will pose an additional issue.

If using Clustered ONTAP, there is an additional consideration covered below.

A typical error message within RHEV-M includes (this is a RHEV 3.3 error):

"Error while executing action Add Storage Connection: Permission settings on the specified path do not allow access to the storage. Verify permission settings on the specified storage path."

Environment

All versions of Red Hat Enterprise Virtualization, all versions of NetApp NFS, all NFS versions (v2, v3, v4, pNFS), and all RHEV NFS domain types.

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content