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
Host info inconsistency #112
Comments
This is most likely related to your problem with #110 too. When a host registers with the server we try to be smart and detect the IP of the host. Unfortunately we just aren't smart enough. The way we do the detection is by looking at the client IP of the TCP connection. What this means is the specific TCP route taken to get to the server impacts the registered IP. So for the server on the right it appears the TCP connection was local, while the server on the left the TCP traffic was private to your VPC. In the end, the best thing to do is to try forcing the host IP. You don't need to delete the hosts, just rerun the agent registration docker command and add |
That seems to have fixed it. I had one agent running on the same node as the Rancher Server. This agent used the docker0 interface to communicate with the Rancher server instead of the actual network interface. |
Catalog code refactor and new feats
Ensure cattle token secret has unique name
The host info sections on my Rancher server are inconsistent. In the agent on the left he host Info IP matches my eth0 interface.
ifconfig
docker0 Link encap:Ethernet HWaddr 56:84:7A:FE:97:99
inet addr:172.17.42.1 Bcast:0.0.0.0 Mask:255.255.0.0
....
However on the agent on the right it matches my docker0 interface:
How is the Host IP selected and should it list the docker0 interface or the host internet interface?
The text was updated successfully, but these errors were encountered: