{"action":"closed","issue":{"url":"https://api.github.com/repos/rancher/rancher/issues/5466","repository_url":"https://api.github.com/repos/rancher/rancher","labels_url":"https://api.github.com/repos/rancher/rancher/issues/5466/labels{/name}","comments_url":"https://api.github.com/repos/rancher/rancher/issues/5466/comments","events_url":"https://api.github.com/repos/rancher/rancher/issues/5466/events","html_url":"https://github.com/rancher/rancher/issues/5466","id":166139378,"number":5466,"title":"Cross-Host Communication Issue","user":{"login":"drdocker","id":14265086,"avatar_url":"https://avatars.githubusercontent.com/u/14265086?v=3","gravatar_id":"","url":"https://api.github.com/users/drdocker","html_url":"https://github.com/drdocker","followers_url":"https://api.github.com/users/drdocker/followers","following_url":"https://api.github.com/users/drdocker/following{/other_user}","gists_url":"https://api.github.com/users/drdocker/gists{/gist_id}","starred_url":"https://api.github.com/users/drdocker/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/drdocker/subscriptions","organizations_url":"https://api.github.com/users/drdocker/orgs","repos_url":"https://api.github.com/users/drdocker/repos","events_url":"https://api.github.com/users/drdocker/events{/privacy}","received_events_url":"https://api.github.com/users/drdocker/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":2,"created_at":"2016-07-18T16:45:35Z","updated_at":"2016-07-18T18:21:57Z","closed_at":"2016-07-18T18:21:57Z","body":"**Rancher Version:** 1.1.1\r\n\r\n**Docker Version:** 1.11.2\r\n\r\n**OS and where are the hosts located? (cloud, bare metal, etc):** CentOS 7 on all boxes - Mix between Cloud and Bare Metal servers\r\n\r\n**Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)**\r\n\r\nSingle Node Rancher Master\r\n3x Rancher Hosts\r\n\r\n**Environment Type: (Cattle/Kubernetes/Swarm/Mesos)**  Cattle!\r\n\r\n**Steps to Reproduce:**\r\n\r\nI've encountered a strange issue as it relates to Cross-Host Communications. Today, I created some new boxes. One box was in OVH's VPS (*Rancher Server* and *Host* containers on this box), the other box was on OVH's bare metal server (same data center - *Rancher Host*), and the last box was in Digital Ocean (*Rancher Host*).\r\n\r\nEach of the boxes were created from scratch, using a single command to setup the latest version of Docker:  `curl -sSL https://get.docker.com/ | sh`\r\n\r\nAfter starting and enabling Docker, I then went to add the host machines.\r\n\r\n*OVH VPS Host*:  For this, from my Rancher administrative page, I selected \"Custom\" Host, and typed in the command that Rancher provided. This includes entering in the `CATTLE_AGENT_IP`, where I typed in the *public* IP of the VPS.\r\n\r\n*OVH Bare Metal Host*: Again, from the administrative page, I selected \"Custom\" Host, and typed in the command that Rancher provided. I also included the `CATTLE_AGENT_IP` -- the public IP of the Bare Metal Machine.\r\n\r\n*Digital Ocean Host*: I selected \"Custom\" Host, and repeated the above steps, including adding the `CATTLE_AGENT_IP`\r\n\r\nAll of my hosts were then registered in Rancher/Cattle, as expected. \r\n\r\nI then added the same container on each of the three hosts.\r\n\r\n**Results:** \r\n\r\n*OVH VPS Host:* Containers worked as expected, and through the Internal Rancher Network Agent IP (provided by selecting the checkbox on the top right of the Hosts page), I was able to ping the *Digital Ocean Host*, but not the OVH Bare Metal Host.\r\n\r\n*OVH Bare Metal Host:* I was able to deploy the container to this host, however, I was *unable* to ping any of the other two hosts. Neither the Digital Ocean Host, nor the OVH VPS Host would reply to my Network Agent ping requests.\r\n\r\n*Digital Ocean Host:* Containers worked as expected, and through the Internal Rancher Network Agent IP, I was able to ping the OVH VPS Host, but not the OVH Bare Metal Host.\r\n\r\nThis unexpected behavior leads to a variety of issues, but namely, I am unable to use a cross-networked load balancer since all of the services on the *OVH Bare Metal Host* come up as a 503 error. \r\n\r\nWhen using a load balancer directly on the *OVH Bare Metal Host*, I am able to see the services located on the host itself, but I am not able to receive responses from any of the other hosts. The load balancer also stays in a permanent? *Initializing* state (my tests ran for 2 hours). While it works, it's not working as expected since it only can see the services located on the same machine as itself.\r\n\r\nHelp! Thanks in advance! 👍 \r\n"}}
{"actor":{"display_login":"drdocker"}}