-
Notifications
You must be signed in to change notification settings - Fork 5.5k
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
FQDNs grains generate errors in IPv6 #52788
Comments
I could be wrong, but it seems like this is behavior that we would like to have, or at least optionally turn off. @saltstack/team-core @saltstack/team-network do you have any thoughts here? |
If I understand the problem, Error 1 will never go away as is an IPv6 that will never have a domain name associated, and I do not see this as an error per se. Error 4 is when an old IPv6 disappear from the resolver, something that, looks like, can happen frequently as there is some kind of temporary IPv6 or something. If this is correct, I would thing that this is neither an error relevant to be logged (maybe a WARNING or an INFO) |
Also ignore NO_DATA errors, as this imply an empty field Fixes saltstack#52788 (cherry picked from commit 816ee23bb11a5bca3930f8e98166f498b5bcee33)
The fix is rebased on master now |
Also ignore NO_DATA errors, as this imply an empty field Fixes saltstack#52788
Description of Issue/Question
My salt-master is over a host that contains IPv4 and IPv6 addresses, and not all the IPv6 can be resolved by a DNS.
The grains in core try to resolve all the IPs, but not all of them can be resolved, so my master log errors like this ones:
Those errors correspond to the HOST_NOT_FOUND and NO_DATA from the socket API.
Setup
Any deployment of develop will recreate the issue
Versions Report
develop
branchThe text was updated successfully, but these errors were encountered: