On 31/01/2024 08:38, Torkil Svensgaard wrote:
Hi
Last week we created an NFS service like this:
" ceph nfs cluster create jumbo "ceph-flash1,ceph-flash2,ceph-flash3" --ingress --virtual_ip 172.21.15.74/22 --ingress-mode keepalive-only "
Worked like a charm. Yesterday we upgraded from 17.2.7 to 18.20.0 and the NFS virtual IP seems to have gone missing in the process:
" # ceph nfs cluster info jumbo { "jumbo": { "backend": [ { "hostname": "ceph-flash1", "ip": "172.21.15.148", "port": 2049 } ], "virtual_ip": null } } "
Service spec:
" service_type: nfs service_id: jumbo service_name: nfs.jumbo placement: count: 1 hosts: - ceph-flash1 - ceph-flash2 - ceph-flash3 spec: port: 2049 virtual_ip: 172.21.15.74 "
I've tried restarting the nfs.jumbo service which didn't help. Suggestions?
Should I have an ingress service with "--ingress-mode keepalive-only"? We created the cluster with the nfs module[1] but looking at the cephadm documentation[2] it looks like that should also have created an ingress service, which is currently missing. [1] https://docs.ceph.com/en/latest/mgr/nfs/#create-nfs-ganesha-cluster [2] https://docs.ceph.com/en/latest/cephadm/services/nfs/#nfs-with-virtual-ip-bu... Mvh. Torkil
Mvh.
Torkil
-- Torkil Svensgaard Sysadmin MR-Forskningssektionen, afs. 714 DRCMR, Danish Research Centre for Magnetic Resonance Hvidovre Hospital Kettegård Allé 30 DK-2650 Hvidovre Denmark Tel: +45 386 22828 E-mail: torkil@drcmr.dk