Hide Forgot
Created attachment 827169 [details] commands run on cluster node explaining more in detail setup and what happened wrong Description of problem: I have a cluster to provide nfs ha server which has the following resources in a group: Resource: vip (class=ocf provider=heartbeat type=IPaddr2) Attributes: ip=10.15.112.227 cidr_netmask=24 Operations: monitor interval=30s (vip-monitor-interval-30s) Resource: havg (class=ocf provider=heartbeat type=LVM) Attributes: volgrpname=shared exclusive=true Operations: monitor interval=60s (havg-monitor-interval-60s) Resource: nfs-shared-fs (class=ocf provider=heartbeat type=Filesystem) Attributes: device=/dev/shared/shared0 directory=/mnt/shared0 fstype=ext4 options= Operations: monitor interval=30s (nfs-shared-fs-monitor-interval-30s) Resource: nfs-server (class=ocf provider=heartbeat type=nfsserver) Attributes: nfs_ip=10.15.112.227 nfs_shared_infodir=/mnt/shared0/nfs nfs_notify_cmd=/usr/sbin/sm-notify Operations: monitor interval=30s (nfs-server-monitor-interval-30s) Resource: nfs-export (class=ocf provider=heartbeat type=exportfs) Attributes: directory=/mnt/shared0 clientspec=* options=rw,async,no_all_squash fsid=290 Operations: monitor interval=60s (nfs-export-monitor-interval-60s) I'm using clvmd+dlm with lvm resource agent to have exclusive activation of the shared disk. /var/lib/nfs directory resides on shared disk (/mnt/shared0/nfs). nfs-server resource is not starting because missing /var/lib/nfs/etab file. Creating this file with touch command and running 'pcs resource cleanup nfs-server' starts the resource correctly. Version-Release number of selected component (if applicable): resource-agents-3.9.5-18.el7.x86_64 How reproducible: always Steps to Reproduce: 1. create cluster resources necessary to run ha nfsserver 2. see nfs-server resource not being started Actual results: nfs-server not being started Expected results: nfs-server started Additional info: /var/lib/nfs/etab is present on the local filesystem and is part of nfs-utils package. nfs-server and nfs-lock are both disabled not to interfere with cluster running them see attached file for more detailed overview of actions run.
I've created a upstream patch that should resolve this. https://github.com/ClusterLabs/resource-agents/pull/357
Does this affect rhel6 as well?
rhel6 is not affected.
I have verified that after upgrading resource-agents to version 3.9.5-20 and repeating the initial scenario from comment 1 nfsserver resource correctly started, moved and that it really can be mounted as nfs from outside of cluster. virt-135$ # rpm -q resource-agents resource-agents-3.9.5-20.el7.x86_64 virt-135# pcs status Cluster name: STSRHTS32645 Last updated: Fri Nov 29 13:26:43 2013 Last change: Fri Nov 29 13:26:15 2013 via cibadmin on virt-134 Stack: corosync Current DC: virt-134 (1) - partition with quorum Version: 1.1.10-20.el7-368c726 3 Nodes configured 6 Resources configured Online: [ virt-134 virt-135 virt-136 ] Full list of resources: virt-fencing (stonith:fence_xvm): Started virt-134 Resource Group: ha-nfsserver vip (ocf::heartbeat:IPaddr2): Started virt-135 havg (ocf::heartbeat:LVM): Started virt-135 nfs-shared-fs (ocf::heartbeat:Filesystem): Started virt-135 nfs-server (ocf::heartbeat:nfsserver): Started virt-135 nfs-export (ocf::heartbeat:exportfs): Started virt-135 PCSD Status: virt-134: Offline virt-135: Offline virt-136: Offline Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: unknown/disabled virt-135$ # pcs resource show vip havg nfs-shared-fs nfs-server nfs-export Resource: vip (class=ocf provider=heartbeat type=IPaddr2) Attributes: ip=10.34.70.159 cidr_netmask=23 Operations: monitor interval=30s (vip-monitor-interval-30s) Resource: havg (class=ocf provider=heartbeat type=LVM) Attributes: volgrpname=ha-vg exclusive=true Operations: monitor interval=60s (havg-monitor-interval-60s) Resource: nfs-shared-fs (class=ocf provider=heartbeat type=Filesystem) Attributes: device=/dev/ha-vg/ha-lv-0 directory=/mnt/shared0 fstype=ext4 options= Operations: monitor interval=30s (nfs-shared-fs-monitor-interval-30s) Resource: nfs-server (class=ocf provider=heartbeat type=nfsserver) Attributes: nfs_ip=10.34.70.159 nfs_shared_infodir=/mnt/shared0/nfs nfs_notify_cmd=/usr/sbin/sm-notify Operations: monitor interval=30s (nfs-server-monitor-interval-30s) Resource: nfs-export (class=ocf provider=heartbeat type=exportfs) Attributes: directory=/mnt/shared0 clientspec=* options=rw,sync fsid=119 Operations: monitor interval=60s (nfs-export-monitor-interval-60s) virt-135$ pcs resource move ha-nfsserver virt-135$ # pcs status Cluster name: STSRHTS32645 Last updated: Fri Nov 29 13:33:26 2013 Last change: Fri Nov 29 13:32:33 2013 via crm_resource on virt-135 Stack: corosync Current DC: virt-134 (1) - partition with quorum Version: 1.1.10-20.el7-368c726 3 Nodes configured 6 Resources configured Online: [ virt-134 virt-135 virt-136 ] Full list of resources: virt-fencing (stonith:fence_xvm): Started virt-134 Resource Group: ha-nfsserver vip (ocf::heartbeat:IPaddr2): Started virt-136 havg (ocf::heartbeat:LVM): Started virt-136 nfs-shared-fs (ocf::heartbeat:Filesystem): Started virt-136 nfs-server (ocf::heartbeat:nfsserver): Started virt-136 nfs-export (ocf::heartbeat:exportfs): Started virt-136 PCSD Status: virt-134: Offline virt-135: Offline virt-136: Offline Daemon Status: corosync: active/enabled pacemaker: active/enabled pcsd: unknown/disabled
This request was resolved in Red Hat Enterprise Linux 7.0. Contact your manager or support representative in case you have further questions about the request.