Open Stack

Hello!

I believe there is not an automated way to do this using Manila itself, or
a config thing you could set,
considering that the controller will have no visibility over all mounts
consuming the volume.

So the consumers will need to re-mount, and even if scripted or automated,
it should be
triggered on each client consuming the share, which is painful. There might
be more users that
faced this issue in the past and could have a way to work it around, so
getting some more input
from other people would be appreciated.

Regards,
carloss

Em ter., 30 de ago. de 2022 às 02:01, Vaibhav <mmilan2006 at gmail.com>
escreveu:

> Dear All,
>
> One of the host running Manila-share service has rebooted.
> After the reboot the LVMs are not mounted on the Manila mount points.
>
> I use LVM Driver with DHSS=False.
>
> default_share_type = default_share_type
> share_name_template = manila-%s
> rootwrap_config = /etc/manila/rootwrap.conf
> api_paste_config = /etc/manila/api-paste.ini
>
> auth_strategy = keystone
> my_ip=192.168.82.2
> enabled_share_backends = lvm
> enabled_share_protocols = NFS
> state_path=/var/lib/manila
>
> [lvm]
> share_backend_name = LVM
> share_driver = manila.share.drivers.lvm.LVMShareDriver
> driver_handles_share_servers = False
> lvm_share_volume_group = VGZunManila
> lvm_share_export_ips = 192.168.82.2
> lvm_share_export_root = $state_path/mnt
>
> After the reboot LVMs are there but they are mounted on their respective
> share location.
>
> Any way to solve this and this to be done automatically?
>
> Regards,
> Vaibhav
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.openstack.org/pipermail/openstack-discuss/attachments/20220905/14bea7a9/attachment.htm>