Happy Friday!
Is it common to NFS-mount /etc/grid-security/vomsdir?
Our newer (htcondor) WN NFS-mount /etc/grid-security/gridmapdir &
/etc/grid-security/vomsdir; the older non-htcondor WN do not (at this
time)
Apparently updating voms package (not happen often, but) wants to write to
/etc/grid-security/vomsdir (or maybe just touch
/etc/grid-security/vomsdir or something).
On the htcondor WN /etc/grid-security/vomsdir is nobody:nobody
root@hd-36-09> touch /etc/grid-security/vomsdir/
touch: setting times of `/etc/grid-security/vomsdir/': Permission denied
My colleague says he's seen the voms pkg update FAIL due to this.
So when updating voms pkg, /etc/grid-security/vomsdir has to be
unmounted, update the voms pkg, then remount it.
What would happen to new jobs that arrive on WN in that time? Fail if
/etc/grid-security/vomsdir is, erm, an empty mountpoint?
Or, is it: "don't update voms pkg when WN running jobs - must be drained."
Then, no worry.
Grateful for advice!
|