-
Notifications
You must be signed in to change notification settings - Fork 26
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Problems with host DNS resolution when configuring services #469
Comments
A similar error occurred with MySQL, and I applied the same fix i.e. adding an IP address in the environment vars. |
The workaround for a lack of working internal dns is to enable the etc_hosts role. In
you need to enable this by adding hosts to this group e.g.
edit: we should probably turn this on by default TBH |
Ah, I thought there should be provision for this, and I just hadn't found it. Will try that now, thanks. |
You can see all the available groups in https://github.com/stackhpc/ansible-slurm-appliance/blob/main/environments/common/inventory/groups. Usually there is a role of the same name with documentation. |
I think it would be friendlier to newbies to have this on by default, yes. |
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: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.
The text was updated successfully, but these errors were encountered: