Skip to content
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

bug: for some reason dns resolving doesnt work in pods after fresh install #64

Open
metacoma opened this issue Aug 9, 2024 · 3 comments
Assignees
Labels
bug Something isn't working

Comments

@metacoma
Copy link
Contributor

metacoma commented Aug 9, 2024

it's affect neo4j deployment

$ kubectl -n context-purple logs purple-neo4j-0 -c install-apoc-plugin                   
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current                                              
                                 Dload  Upload   Total   Spent    Left  Speed                                                
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: github.com   
Warning: Problem : timeout. Will retry in 1 seconds. 3 retries left.                                                         
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: github.com   
Warning: Problem : timeout. Will retry in 2 seconds. 2 retries left.                                                         
  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0curl: (6) Could not resolve host: github.com   
Warning: Problem : timeout. Will retry in 4 seconds. 1 retries left.                             

some additional diagnostic from the nicolaka/netshoot pod

tmp-shell  ~  ping github.com
ping: github.com: Name has no usable address

 tmp-shell  ~  cat /etc/resolv.conf
nameserver 10.43.0.10
search default.svc.cluster.local svc.cluster.local cluster.local 
options ndots:5

tmp-shell  ~  host github.com 10.43.0.10
Using domain server:
Name: 10.43.0.10
Address: 10.43.0.10#53
Aliases: 
@metacoma metacoma added the bug Something isn't working label Aug 9, 2024
@metacoma metacoma self-assigned this Aug 9, 2024
@metacoma metacoma added this to Mindwm Aug 9, 2024
@metacoma
Copy link
Contributor Author

metacoma commented Aug 9, 2024

the problem is with the ending dot .

tmp-shell  ~  host google.com.
google.com has address 142.251.32.46

tmp-shell  ~  host github.com.
github.com has address 140.82.116.3

@metacoma
Copy link
Contributor Author

metacoma commented Aug 9, 2024

Fixed by #65

@metacoma metacoma closed this as completed Aug 9, 2024
@github-project-automation github-project-automation bot moved this to Done in Mindwm Aug 9, 2024
@omgbebebe
Copy link
Contributor

second run of make mindwm_lifecycle fails with

user@mindwm-dev1:~/work/dev/mindwm-gitops$ time make mindwm_lifecycle
k3s-uninstall.sh ; \
sleep 10 # :)
/bin/sh: 1: k3s-uninstall.sh: not found
docker version -f json | jq -e '.Server.ApiVersion | select(tonumber >= 1.46)';
"1.46"
grep -q '^search [^\.]' /etc/resolv.conf || exit 0
cat<<EOF
Please turn off search domain option from your resolv.conf file
More details here:
https://github.com/mindwm/mindwm-gitops/issues/64
https://github.com/k3s-io/k3s/issues/5567
https://github.com/k3s-io/k3s/issues/9286

the search value already set as mindwm. I suppose it needs to check this case in the script.

@omgbebebe omgbebebe reopened this Aug 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
Status: Done
Development

No branches or pull requests

2 participants