Forums

Home / Forums

You need to log in to create posts and topics. Login · Register

NFS issue after upgrading from 3.1.0 to 3.3.0


shulemmosko
33 Posts
October 29, 2024, 3:20 am

Hi we have a 5 node cluster with 2 nodes running nfs after upgrading from 3.1.0 to 3.3.0 only one node works the second node cannot create the podman container. see below it keeps on going in circles Pull, Create, Cleanup, Remove

root@PS-NODE5:/etc/containers# podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES

root@PS-NODE5:/etc/containers# podman events
2024-10-28 23:10:15.524144228 -0400 EDT container cleanup 25dd6036595f5673488cdadef1e5adf86fbdeafae9b6f3bb9d7ac6d2cc444ae1 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)
2024-10-28 23:10:15.708600384 -0400 EDT container remove 25dd6036595f5673488cdadef1e5adf86fbdeafae9b6f3bb9d7ac6d2cc444ae1 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)
2024-10-28 23:10:16.02409281 -0400 EDT container create a1e156d91f03a8e42dc3b22de4f029ba84a7da809a46605e82ce1caac3b4da32 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)
2024-10-28 23:10:15.974302608 -0400 EDT image pull localhost/petasan-nfs-ganesha:3.2.0
2024-10-28 23:10:19.732305927 -0400 EDT container cleanup a1e156d91f03a8e42dc3b22de4f029ba84a7da809a46605e82ce1caac3b4da32 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)
2024-10-28 23:10:19.921323866 -0400 EDT container remove a1e156d91f03a8e42dc3b22de4f029ba84a7da809a46605e82ce1caac3b4da32 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)
2024-10-28 23:10:22.024150438 -0400 EDT container create c86650ea03d943dd420d274171447327955625e1d6bf7e3d9eb0ff342e34f5d1 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)
2024-10-28 23:10:21.975058124 -0400 EDT image pull localhost/petasan-nfs-ganesha:3.2.0
2024-10-28 23:10:52.950969808 -0400 EDT container cleanup c86650ea03d943dd420d274171447327955625e1d6bf7e3d9eb0ff342e34f5d1 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)
2024-10-28 23:10:53.133425554 -0400 EDT container remove c86650ea03d943dd420d274171447327955625e1d6bf7e3d9eb0ff342e34f5d1 (image=localhost/petasan-nfs-ganesha:3.2.0, name=NFS-172-16-1-2)

 

Please advise.

Thank you!!

#1

shulemmosko
33 Posts
October 29, 2024, 4:35 am

Ok i got it fixed, for some reason the server was running nfs-server and was binding to the nfs port.

i just stopped and disabled the nfs-server service and the container started successfully.

 

Thanks anyways!

#2