Created attachment 1084633 [details] sosreport of the server Description of problem: /etc/corosync/corsync.conf file missing after multiple nfs-ganesha disable/enable, due to which not able to setup the ganesha cluster Version-Release number of selected component (if applicable): nfs-ganesha-2.2.0-9.el7rhgs.x86_64 glusterfs-3.7.5-0.3.el7rhgs.x86_64 How reproducible: Twice Steps to Reproduce: 1. Multiple times executing gluster nfs-ganesha enable/disable 2. /etc/corosync/corsync.conf file is missing /var/log/messages: Oct 20 12:45:24 dhcp35-194 systemd: Started PCS GUI and remote configuration interface. Oct 20 12:45:24 dhcp35-194 systemd: Starting Corosync Cluster Engine... Oct 20 12:45:24 dhcp35-194 corosync[24640]: [MAIN ] Can't read file /etc/corosync/corosync.conf reason = (No such file or directory) Oct 20 12:45:24 dhcp35-194 corosync[24640]: [MAIN ] Corosync Cluster Engine exiting with status 8 at main.c:1207. Oct 20 12:45:24 dhcp35-194 corosync: Starting Corosync Cluster Engine (corosync): [FAILED] Oct 20 12:45:24 dhcp35-194 systemd: corosync.service: control process exited, code=exited status=1 Oct 20 12:45:24 dhcp35-194 systemd: Failed to start Corosync Cluster Engine. Oct 20 12:45:24 dhcp35-194 systemd: Dependency failed for Pacemaker High Availability Cluster Manager. Oct 20 12:45:24 dhcp35-194 systemd: Oct 20 12:45:24 dhcp35-194 systemd: Unit corosync.service entered failed state. Oct 20 12:45:24 dhcp35-194 systemd: Starting NFS status monitor for NFSv2/3 locking.... Oct 20 12:45:24 dhcp35-194 rpc.statd: Statd service already running! Oct 20 12:45:24 dhcp35-194 systemd: nfs-ganesha-lock.service: control process exited, code=exited status=1 Oct 20 12:45:24 dhcp35-194 systemd: Failed to start NFS status monitor for NFSv2/3 locking.. Oct 20 12:45:24 dhcp35-194 systemd: Unit nfs-ganesha-lock.service entered failed state. Oct 20 12:45:24 dhcp35-194 systemd: Started NFS-Ganesha file server. Oct 20 12:46:01 dhcp35-194 systemd: Starting Session 1784 of user root. Oct 20 12:46:01 dhcp35-194 systemd: Started Session 1784 of user root. Oct 20 12:46:28 dhcp35-194 systemd: Starting NFS status monitor for NFSv2/3 locking.... Oct 20 12:46:28 dhcp35-194 rpc.statd: Statd service already running! Oct 20 12:46:28 dhcp35-194 systemd: nfs-ganesha-lock.service: control process exited, code=exited status=1 Oct 20 12:46:28 dhcp35-194 systemd: Failed to start NFS status monitor for NFSv2/3 locking.. Oct 20 12:46:28 dhcp35-194 systemd: Unit nfs-ganesha-lock.service entered failed state. Actual results: /etc/corosync/corsync.conf file is missing Expected results: /etc/corosync/corsync.conf file should not be missing Additional info:
*** Bug 1273292 has been marked as a duplicate of this bug. ***
Request Apeksha to reproduce and provide us the setup. Lowering the priority till then
I have checked the setup. Below message is just a warning and doesn't impact pcs cluster auth command- [2016-02-17T20:25:49.970444 #30365] WARN -- : Cannot read config 'corosync.conf' from '/etc/corosync/corosync.conf': No such file or directory - /etc/corosync/corosync.conf When I have disabled firewall and selinux, the authentication went through successfully.
Above log message is just a warning and doesn't affect cluster setup. This warning is logged because we do not create this configuration file prior to cluster setup but is auto-generated as part of cluster creation. The actual reason behind setup failure is selinux or firewalld issue. Based on the above, closing this bug. Please re-open if you run into it.