kricud commented on issue #5491: URL: https://github.com/apache/cloudstack/issues/5491#issuecomment-926650966
@Hudratronium loot of assumptions on what you have. Remove global setting “secstorage.nfs.version” leave it blank. On KVM host newest possible version will be used supported by server nfs4.1. Confirm that KVM host and NFS host have same domain name if no in /etc/idmapd.conf fix domain name on ACS/KVM so that your NFS mounts with root:root permissions. (NFSv4 works differently than NFSv3 more in link) https://man7.org/linux/man-pages/man5/nfsidmap.5.html For SSVM Infrastructure > Secondary Storage > click on storage > Settings > Click on Pencil/Edit type “3” > press OK. > destroy SSVM Everywhere except SSVM you will have NFSv4 and for SSVM you will have NFSv3 as you can’t set idmap persistently for domain on it. If you have doomsday disable NFSv4 on server fix ACS and then enable it. NFSv3 will work as clock. Probably there was case way “secstorage.nfs.version” was introduced as global setting. I cant come up with anything decent today. Your issue is bug but why would you want to use it this way. I can’t answer to it. (enforcement, compliance) -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@cloudstack.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
