"M" == hereiam <hereiam@mit.edu> writes:
Hi Mike, M> Hi Roland, Thank you very much for the updates, glad to see my M> little permissions patch made it in! yup, thanks again for reporting. M> I've got another potential one for you - I've noticed that even M> after the new updates, and even when defining Network Mounts for M> <headnode>:/srv/apps and <headnode>:/srv/data as /apps and /data M> for compute nodes, they don't automount for some reason. When I M> manually mount those on each node: >>>> mount -t nfs <headnode>:/srv/data /data mount -t nfs >>>> <headnode>:/srv/apps /apps M> they work fine and persist until the next reboot. I'm not sure M> which file(s) control pushing the network mounts to the compute M> nodes, though I do notice that the <headnode>:/srv/ql-common and M> <headnode>:/srv/apps/chroots/focal do mount correctly. M> Any idea what might be causing this? I've reproduced it on both M> my real, legit cluster with identical, rack-mount hardware and my M> cobbled-together laptop cluster. We can't reproduce this. Note that newly defined mounts are available only after a reboot of the nodes and only after accessing the mount point (automount). You can use the context-menu entry 'Preview config' when on a host in the Enclosure View to see the generated files for this node when it boots. Best, Roland