Hide Forgot
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html/Administration_Guide/sect-NFS.html#idp4816928 Section Number and Name: 7.2.3.3. Configuring NFS-Ganesha using Gluster CLI Describe the issue: This section calls for the user to start the pacemaker service directly with the 'systemctl start pacemaker' command (RHEL 7). However, the service will fail to start due to a corosync dependency. The corosync service will not start because it's configuration file is dynamically created by the nfs-ganesha service, which has not yet been started. Suggestions for improvement: Remove the instructions to start the pacemaker service. This step is not needed and only leads to a failed service at this point in the documented steps. Additional information:
The instruction to start the pacemaker service, that was earlier added under " 7.2.3.3.1. Prerequisites to run NFS-Ganesha" is now removed. http://jenkinscat.gsslab.pnq.redhat.com:8080/job/doc-Red_Hat_Gluster_Storage-3.1-3.1.2-Stage_Administration_Guide%20%28html-single%29/lastSuccessfulBuild/artifact/tmp/en-US/html-single/index.html#sect-NFS_Ganesha
Verified the bug with the newly provided doc link: http://10.34.3.139:8080/view/Gluster/job/doc-Red_Hat_Gluster_Storage-3.1.2-Administration_Guide%20%28html-single%29/ws/tmp/en-US/html-single/index.html#sect-NFS_Ganesha and under section "7.2.3.3.1. Prerequisites to run NFS-Ganesha", there is no statement saying start the pacemaker service. Hence, marking this bug as Verified.
Admin Guide is published live on the customer portal: https://access.redhat.com/documentation/en-US/Red_Hat_Storage/3.1/html-single/Administration_Guide/index.html#sect-NFS_Ganesha