Comment 1 for bug 2073498

Added the charm-ceph-fs project as the bug may be due to that. See this comment [1] from the review for the manila-ganesha charm [2]

> Looking through the logs of the latest change, I can see that removing the ceph share is failing due to a timeout (error -110 == ETIMEDOUT). Looking at the Ceph FS logs, I can see that the mds server is restarted very regularly on both instances - each time that a config changed or assess status call is invoked and I think this is playing into the failures seen here.

> Looking at the change for https://review.opendev.org/c/openstack/charm-ceph-fs/+/916693, I can see that the mds service will be restarted every time that the config changed hook is run without worrying about whether it is actually needed or not. Essentially, this change is trying to make sure that the mds keys are updated - without consideration as to whether the ceph keys actually changed or not. This is causing very frequent restart and recovery of the mds servers.

[1] https://review.opendev.org/c/openstack/charm-manila-ganesha/+/917334/comments/c9e32574_add8dc07
[2] https://review.opendev.org/c/openstack/charm-manila-ganesha/+/917334