| 2013-06-25 08:07:40 |
Abdelaali SADKI |
description |
For a scaled OpenShift Origin environment (multi-nodes architecture), HAProxy can't see the additional nodes and says: "L4CON: No route to host" on the HAProxy status page or "E, [2013-06-25T03:38:22.020229 #23515] ERROR -- : Unable to get gear's IP address for 51c44f9c2d9ee2bf29000547-mydomain.example.com: getaddrinfo: Name or service not known - using default 10.0.0.7".
Actually, this bug is related to the firewalls rules so I fixed it by:
- Adding manually a rule to OpenShiftOriginSecurityGroup:
nova secgroup-add-rule OpenShiftOriginSecurityGroup tcp 35531 35531 0.0.0.0/0
- Opening manually port 35531 on each node:
lokkit -p 35531:tcp
After these instructions, we can see on the status page that HAProxy can reach all the nodes "Layer7 check passed: HTTP content check matched"
Regards |
For a scaled OpenShift Origin environment (multi-nodes architecture), HAProxy can't see the additional nodes and says: "L4CON: No route to host" on the HAProxy status page or "E, [2013-06-25T03:38:22.020229 #23515] ERROR -- : Unable to get gear's IP address for 51c44f9c2d9ee2bf29000547-mydomain.example.com: getaddrinfo: Name or service not known - using default 10.0.0.7" on the validate_config.log file.
Actually, this bug is related to the firewalls rules so I fixed it by:
- Adding manually a rule to OpenShiftOriginSecurityGroup:
nova secgroup-add-rule OpenShiftOriginSecurityGroup tcp 35531 35531 0.0.0.0/0
- Opening manually port 35531 on each node:
lokkit -p 35531:tcp
After these instructions, we can see on the status page that HAProxy can reach all the nodes "Layer7 check passed: HTTP content check matched".
Regards |
|
