You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Steps to Reproduce:
Upgraded infra to use AWS ALB instead of ELB with proxy policies.
Security has not changed, I could manually curl and ping the container's IP address from the stack host as well as rancher-agent container.
Results:
Agents can connect as before, hosts show as online, containers can be deployed, UI works. Upon deploying, services with health checks are stuck in "initialising" or "reinitialising" (restart) state. Same of load balancers. Restarting an existing "running" container that was deployed before the switch results in "initialising" state.
Expected:
Containers pass as healthy.
The text was updated successfully, but these errors were encountered:
I was wondering about that. But sockets work without a problem and so does SSL stuff. I'm surprised that load balancer affects health checks which from my understanding are ran from rancher agents using Rancher networking - in my case a single host.
Rancher Versions:
Server: 1.1.4
Docker Version:
OS and where are the hosts located? (cloud, bare metal, etc):
AWS EC2
Setup Details: (single node rancher vs. HA rancher, internal DB vs. external DB)
Single + external DB
Environment Type: (Cattle/Kubernetes/Swarm/Mesos)
Cattle
Steps to Reproduce:
Upgraded infra to use AWS ALB instead of ELB with proxy policies.
Security has not changed, I could manually curl and ping the container's IP address from the stack host as well as rancher-agent container.
Results:
Agents can connect as before, hosts show as online, containers can be deployed, UI works. Upon deploying, services with health checks are stuck in "initialising" or "reinitialising" (restart) state. Same of load balancers. Restarting an existing "running" container that was deployed before the switch results in "initialising" state.
Expected:
Containers pass as healthy.
The text was updated successfully, but these errors were encountered: