Adding disable-skip-name-resolve to mysql #206
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The scripts that handle user creation in XDMoD rely on hostnames when specifying a user's host ( as opposed to using IP Addresses ). Without this setting in place all authentication attempts from the xdmod container fail.
aebruno
approved these changes
Mar 13, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The changes in this PR arose from a desire to be able to choose between having a fully configured & populated XDMoD database & a fully configured but empty XDMoD database. The method of having a fully configured by empty database, from investigation, seemed to be: remove / rename the
database/xdmod.dumpfile and the included bash scripts would take care of the rest. Upon testing it was found that the scripts that handle the setup of users and databases for XDMoD, when the dump is not present, were relying on MariaDB allowing / using hostname's for database users. This conflicted with a new(-ish) MariaDB configurationskip-name-resolvebeing enabled, which means that all database userhostswould need to be IP Addresses not hostnames, this was causing said scripts to error out due to authentication errors.This PR simply disables the
skip-name-resolveconfiguration option so that we can use hostnames as user hosts again.