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

pods can not accessible routing issue. #159

Open
ab-aritrab opened this issue May 10, 2019 · 2 comments
Open

pods can not accessible routing issue. #159

ab-aritrab opened this issue May 10, 2019 · 2 comments

Comments

@ab-aritrab
Copy link

scenerio :
server : centos IP: 10.14.x.56
where install ./install-openshift.sh
domain name: aritrabiswas.tk (public IP 122.x.x.x)
users name: xxx
password: xxx
port: 8443
TLS auth

  1. yes
  2. No (chose)

after installation: it was showing
oc login -u xxx -p xxx https://console.aritrabiswas.tk:8443


Login successful.

[# prerequisite are installed as same as instructed in the video]

after the creation of pods successfully, unable to access pods through web..

my project name HelloWorld
pods name nginx-test
URL to access: http://nginx-test-helloworld.apps.aritrabiswas.tk
what's wrong with my configuration.???

@weslcurt
Copy link

Not sure if this is your problem but I see DNSMASQ being enabled and NetworkManager being restarted. Once that happens it creates this file in this directory: /etc/NetworkManager/dispatcher.d/99-origin-dns.sh.
In my case, this appears to change "nameserver 8.8.8.8" in resolv.conf to my local IP. I can't resolve to the project's exposed address because DNS is pointing at the server's internal IP address.

If this is what is actually happening, I am not sure how this is working for anyone without modification.

@srinivasraja54
Copy link

Not sure if this is your problem but I see DNSMASQ being enabled and NetworkManager being restarted. Once that happens it creates this file in this directory: /etc/NetworkManager/dispatcher.d/99-origin-dns.sh.
In my case, this appears to change "nameserver 8.8.8.8" in resolv.conf to my local IP. I can't resolve to the project's exposed address because DNS is pointing at the server's internal IP address.

If this is what is actually happening, I am not sure how this is working for anyone without modification.

Not sure if this is your problem but I see DNSMASQ being enabled and NetworkManager being restarted. Once that happens it creates this file in this directory: /etc/NetworkManager/dispatcher.d/99-origin-dns.sh.
In my case, this appears to change "nameserver 8.8.8.8" in resolv.conf to my local IP. I can't resolve to the project's exposed address because DNS is pointing at the server's internal IP address.

If this is what is actually happening, I am not sure how this is working for anyone without modification.

I'm able to fix this issue. Check this PR -> #166

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants