.The `nfs-server` must be disabled on the NFS Ganesha node
When the `nfs-server` service is running on the NFS Ganesha node, an attempt to start the NFS Ganesha instance after its installation fails. To work around this issue, ensure that `nfs-server` is stopped and disabled on the NFS Ganesha node before installing NFS Ganesha. To do so:
# systemctl disable nfs-server
# systemctl stop nfs-server
Description of problem:
Stopping/disabling kNFS service required before installing NFS-Ganesha via ceph-ansible.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Configured ceph-ansible to have a NFS role.
2. Ran ansible-playbook (site.yml)
3. After installation, Check for the nfs-ganesha service. It fails to start.
For details refer BZ https://bugzilla.redhat.com/show_bug.cgi?id=1452762
The exact name of the service is "nfs-server". In your description on this bug, everywhere you say "nfs-service" should be "nfs-server".
Why was nfs-server running in the first place?
Looks like a system misconfiguration to me.
I get that this might be a system misconfiguration, but why wouldn't ceph-ansible be able to stop the service if it is running in order to continue the installation?
Ok, so this sounds more like a request.
I didn't get that this was on purpose.
I guess we can if the service runs and stop it/disable it.
However, I'm just really hesitant changing the system configuration, if kNFS is running it might be for a good reason.
The best thing we should do IMHO is to check if the service runs, fail the playbook and ask to stop it before pursuing the installation.
Is that acceptable to everyone?
(In reply to leseb from comment #10)
> Ok, so this sounds more like a request.
> I didn't get that this was on purpose.
> I guess we can if the service runs and stop it/disable it.
> However, I'm just really hesitant changing the system configuration, if kNFS
> is running it might be for a good reason.
> The best thing we should do IMHO is to check if the service runs, fail the
> playbook and ask to stop it before pursuing the installation.
> Is that acceptable to everyone?
When we do the manual way of installing nfs-ganesha, it is mandatory to stop and disable kNFS before installing nfs-ganesha-rgw. NFS-Ganesha will not start if another NFS instance is running.
As per the doc:
" If the nfs-service service is running, stop and disable it:
# systemctl stop nfs-server.service
# systemctl disable nfs-server.service "
As we are automating nfs-ganesha-rgw installation in 3.0, it will be better to stop and disable nfs-server.service via ceph-ansible.
Here is a PR that stops the service before the nfs-ganesha service can be started:
The above PR has been merged. Ceph-ansible now stops nfs-server via systemd if before it start nfs-ganesha.