-
Notifications
You must be signed in to change notification settings - Fork 38
Closed
Description
Following the README procedure, I found that stackhpc.nfs failed at the point of trying to mount NFS because it couldn't resolve the hostname of the Slurm control node:
TASK [stackhpc.nfs : mount the filesystem] ***************************************************************************************************************************************************************************************************
fatal: [slurmtest03-login-0]: FAILED! => {
"changed": false
}
MSG:
Error mounting /home: mount.nfs: Failed to resolve server slurmtest03-control: Name or service not known
fatal: [slurmtest03-compute-1]: FAILED! => {
"changed": false
}
MSG:
Error mounting /home: mount.nfs: Failed to resolve server slurmtest03-control: Name or service not known
fatal: [slurmtest03-compute-0]: FAILED! => {
"changed": false
}
MSG:
Error mounting /home: mount.nfs: Failed to resolve server slurmtest03-control: Name or service not known
I see there has been previous discussion about whether to use IPs or hostnames.
Can work around this for now with custom SSH config, but I think this should be documented more explicitly.
Metadata
Metadata
Assignees
Labels
No labels