Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
I manually mounted a NFS export at a different mountpoint (/mnt/condor-qsjs) than was in the cluster.conf, and for a different reason, and the netfs RA refused to mount the export when it tried to start the cluster service.  The logs showed:

[netfs] Device 192.168.122.176:/opt/condor is mounted on /mnt/condor-qsjs instead of /mnt/condor-schedd1
unmounting /mnt/condor-schedd1
[netfs] Calling 'umount -f /mnt/condor-schedd1'
[netfs] Sending SIGTERM to processes on /mnt/condor-schedd1


Version-Release number of selected component (if applicable):
resource-agents-3.9.2-7.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:

Fix for issue.

https://github.com/ClusterLabs/resource-agents/commit/9a6681831079bc05f0b4da07ec5058ca73aa7272

    Technical note added. If any revisions are required, please edit the "Technical Notes" field
    accordingly. All revisions will be proofread by the Engineering Content Services team.
    
    New Contents:
Cause: netfs script doesn't check if file system is a network file system before denying multiple mounts

Consequence: you can't mount network filesystems twice

Fix: netfs script now verifies if file system is a network filesystem and if it is, it allows multiple mounts

Result: Multiple network file system mounts of the same filesystem are allowed

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2012-0947.html