exportfs resource monitor operation fails when clientspec uses a short hostname but succeeds with FQDN

Solution Verified - Updated -

Issue

  • exportfs resource monitor operation fails when clientspec uses a short hostname but succeeds with FQDN, or vice-versa.
  • exportfs resource monitor operation fails when clientspec uses a non-canonical hostname.
  • exportfs resource monitor operation fails immediately after start operation succeeds.
  • exportfs resource loops continuously through start success and monitor failure.
  • Does the exportfs resource agent depend on hostname resolution (e.g., DNS or /etc/hosts)?

Environment

  • Red Hat Enterprise Linux Server 6, 7, or 8 (with the High Availability Add-on)
  • Pacemaker

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