Unable to mount PersistentVolume when NFS service uses FQDN in RHOCP 4

Solution Verified - Updated -

Issue

  • Cannot use NFS server configured as pods in RHOCP 4 cluster for PersistentVolume via service FQDN, like nfs-server.build.svc.cluster.local.

  • The pod stuck in ContainerCreating state with below error:

Output: mount.nfs: Failed to resolve server nfs-server.build.svc.cluster.local: Name or service not known
  • Changing the Service FQDN to ClusterIP works fine and volume gets mounted onto the pod.

Environment

  • Red Hat OpenShift Container Platform (RHOCP) 4

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