Hi Oliver,

Thank you! could you please share your config + what proto are you using for the NFS server? 

How does kolla-ansible mount NFS share on compute nodes on what container (libvirt or nova_compute?) because in my case it's not able to mount :( 

On Tue, Mar 5, 2024 at 5:40 PM Oliver Weinmann <oliver.weinmann@me.com> wrote:
Hi Satish,

I’m using NFS in kolla-Ansible and I think your problem is this:

mount.nfs: Protocol not supported

By default it will try to use NFS 4.1. I’m using OmniOS as a storage system and this only support NFS 4 and not 4.1. what storage system are you using?

In my case I switched to NFS 3. When I’m back at work tomorrow, I can send you my config.

If I remember correctly you have to set this in the nfs_shares file.

For stability I can’t really say much since I’m using Ceph as a main storage system.

Cheers,
Oliver

Von meinem iPhone gesendet

Am 05.03.2024 um 22:56 schrieb Satish Patel <satish.txt@gmail.com>:


Hi Sean, 

I have stupid question, How does vm running on compute nodes talk to NFS block volume? Do I need to mount NFS on compute nodes and if yes then at what location?  

On Tue, Mar 5, 2024 at 3:49 PM Satish Patel <satish.txt@gmail.com> wrote:
Hello Sean,

I've configured NFS v4 but still I am seeing cinder-volume@nfs service is down and nothing interesting in logs (I have turned on DEBUG also). What could be the problem? I have just found out that this is not the 2023.1 release but the Zed release of openstack. 

2024-03-05 20:39:35.855 150 DEBUG oslo_concurrency.processutils [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs -o vers=4,minorversion=1 192.168.18.245:/volume1/ISO /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332" returned: 32 in 0.697s execute /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:422
2024-03-05 20:39:35.857 150 DEBUG oslo_concurrency.processutils [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] 'sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs -o vers=4,minorversion=1 192.168.18.245:/volume1/ISO /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332' failed. Not Retrying. execute /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:473
2024-03-05 20:39:35.858 150 ERROR os_brick.remotefs.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Failed to mount 192.168.18.245:/volume1/ISO, reason: mount.nfs: Protocol not supported
: oslo_concurrency.processutils.ProcessExecutionError: Unexpected error while running command.
2024-03-05 20:39:35.859 150 DEBUG os_brick.remotefs.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Failed to do pnfs mount. _mount_nfs /var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/remotefs/remotefs.py:157
2024-03-05 20:39:35.860 150 DEBUG oslo_concurrency.processutils [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs 192.168.18.245:/volume1/ISO /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 execute /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:384
2024-03-05 20:39:36.753 150 DEBUG oslo_concurrency.processutils [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf mount -t nfs 192.168.18.245:/volume1/ISO /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332" returned: 0 in 0.892s execute /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:422
2024-03-05 20:39:36.754 150 DEBUG os_brick.remotefs.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Mounted 192.168.18.245:/volume1/ISO using nfs. _mount_nfs /var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/remotefs/remotefs.py:152
2024-03-05 20:39:36.755 150 DEBUG cinder.volume.drivers.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Available shares ['192.168.18.245:/volume1/ISO'] _ensure_shares_mounted /var/lib/kolla/venv/lib/python3.10/site-packages/cinder/volume/drivers/remotefs.py:358
2024-03-05 20:39:36.756 150 DEBUG cinder.volume.drivers.nfs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] NAS variable secure_file_permissions setting is: false set_nas_security_options /var/lib/kolla/venv/lib/python3.10/site-packages/cinder/volume/drivers/nfs.py:432
2024-03-05 20:39:36.757 150 WARNING cinder.volume.drivers.nfs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] The NAS file permissions mode will be 666 (allowing other/world read & write access). This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NFS configuration.
2024-03-05 20:39:36.757 150 DEBUG cinder.volume.drivers.nfs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] NAS secure file operations setting is: false set_nas_security_options /var/lib/kolla/venv/lib/python3.10/site-packages/cinder/volume/drivers/nfs.py:458
2024-03-05 20:39:36.758 150 WARNING cinder.volume.drivers.nfs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] The NAS file operations will be run as root: allowing root level access at the storage backend. This is considered an insecure NAS environment. Please see https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html for information on a secure NAS configuration.
2024-03-05 20:39:36.759 150 DEBUG cinder.volume.drivers.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Loading shares from /etc/cinder/nfs_shares. _load_shares_config /var/lib/kolla/venv/lib/python3.10/site-packages/cinder/volume/drivers/remotefs.py:597
2024-03-05 20:39:36.760 150 DEBUG cinder.volume.drivers.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] shares loaded: {'192.168.18.245:/volume1/ISO': None} _load_shares_config /var/lib/kolla/venv/lib/python3.10/site-packages/cinder/volume/drivers/remotefs.py:629
2024-03-05 20:39:36.761 150 DEBUG os_brick.remotefs.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Already mounted: /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 mount /var/lib/kolla/venv/lib/python3.10/site-packages/os_brick/remotefs/remotefs.py:105
2024-03-05 20:39:36.761 150 DEBUG cinder.volume.drivers.remotefs [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Available shares ['192.168.18.245:/volume1/ISO'] _ensure_shares_mounted /var/lib/kolla/venv/lib/python3.10/site-packages/cinder/volume/drivers/remotefs.py:358
2024-03-05 20:39:36.762 150 DEBUG oslo_concurrency.processutils [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf stat -f -c %S %b %a /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 execute /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:384
2024-03-05 20:39:37.458 150 DEBUG oslo_concurrency.processutils [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] CMD "sudo cinder-rootwrap /etc/cinder/rootwrap.conf stat -f -c %S %b %a /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332" returned: 0 in 0.696s execute /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:422
2024-03-05 20:39:37.460 150 DEBUG oslo_concurrency.processutils [None req-51d22088-acf4-4dc6-a858-828cc3eb9394 - - - - - -] Running cmd (subprocess): sudo cinder-rootwrap /etc/cinder/rootwrap.conf du -sb --apparent-size --exclude *snapshot* /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 execute /var/lib/kolla/venv/lib/python3.10/site-packages/oslo_concurrency/processutils.py:384

On Tue, Mar 5, 2024 at 12:55 PM Satish Patel <satish.txt@gmail.com> wrote:
Thank you for detailed information,  I would like to use NFS and see how it works. My end goal is to use iSCSI for cinder volume service. 

Do you think switching to NFS v4 will fix the problem in my case. My setup is super simple but somehow it just doesn't like NFS and cinder-volume service is showing down even all the permission and configs are correct. 

On Fri, Mar 1, 2024 at 9:19 AM <smooney@redhat.com> wrote:
On Fri, 2024-03-01 at 09:10 -0500, Satish Patel wrote:
> It Looks like everyone hates NFS and nobody uses it :)
for cidner unless its with a hardware san there are may better options

for better or worse a non 0 numbner of peole decide to put nova's /var/lib/nova/instances directory on NFS shares
instead of using somehting like ceph
>
> On Tue, Feb 27, 2024 at 11:31 PM Satish Patel <satish.txt@gmail.com> wrote:
>
> > Folks,
> >
> > I am configuring NFS for the cinder backend but somehow it doesn't go
> > well. I am running kolla-ansible with the 2023.1 release.
> >
> > cinder.conf
> >
> > [DEFAULT]
> > enabled_backends = volumes-ssd,volumes-nfs
> >
> > [volumes-nfs]
> > volume_driver = cinder.volume.drivers.nfs.NfsDriver
> > volume_backend_name = volumes-nfs
> > nfs_shares_config = /etc/cinder/nfs_shares
> > nfs_snapshot_support = True
> > nas_secure_file_permissions = False
> > nas_secure_file_operations = False
> >
> > Inside the cinder_volume docker container I can see it mounts NFS
> > automatically and directory permissions is also cinder:cinder also I am
> > able to write on NFS share also so it's not a permission issue also.
> >
> > $ docker exec -it cinder_volume mount | grep nfs
> > 192.168.18.245:/volume1/NFS on
> > /var/lib/cinder/mnt/1ec32c051aa5520a1ff679ce879da332 type nfs
> > (rw,relatime,vers=3,rsize=131072,wsize=131072,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,mountaddr=192.16
> > 8.18.245,mountvers=3,mountport=892,mountproto=udp,local_lock=none,addr=192.168.18.245)
nfs v3 should not be used with nova instances and when used for cinder voume there are some know bugs or feature partiy
gaps like live extend.
qemu recommends 4.2 as a minium version to mitigate the massive locking issues with v3 and for some other feature such
as spares file support.  nfs is not a bad idea in general, its fine to use with manial but putting block storage on an
NFS share is generally a bad idea so its not a great fit for cinder/novas usage. for services like glance or manila its
fine.

> >
> > But service is still showing down.
> >
> > > cinder-volume    | os-ctrl2@volumes-nfs  | nova | enabled | down  |
> > 2024-02-28T04:13:11.000000 |
> >
> > In logs I am seeing these 3 lines but then no activity in logs even after
> > restarting the container so that is very strange.
> >
> > 2024-02-28 04:13:12.995 153 ERROR os_brick.remotefs.remotefs [None
> > req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] Failed to mount
> > 192.168.18.245:/volume1/NFS, reason: mount.nfs: Protocol not supported
> > : oslo_concurrency.processutils.ProcessExecutionError: Unexpected error
> > while running command.
> > 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None
> > req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file
> > permissions mode will be 666 (allowing other/world read & write access).
> > This is considered an insecure NAS environment. Please see
> > https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html
> > for information on a secure NFS configuration.
> > 2024-02-28 04:13:13.501 153 WARNING cinder.volume.drivers.nfs [None
> > req-6bcb8eab-6aa6-4c36-9a7a-ed673c39dcbc - - - - - -] The NAS file
> > operations will be run as root: allowing root level access at the storage
> > backend. This is considered an insecure NAS environment. Please see
> > https://docs.openstack.org/cinder/latest/admin/blockstorage-nfs-backend.html
> > for information on a secure NAS configuration.
> >
> > Has anyone configured NFS and noticed any behavior?
> >
> >
> >
> >