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

[release-4.8] Bug 2053720: Avoid dynamically allocated port range for haproxy #171

Commits on Feb 15, 2022

  1. Avoid dynamically allocated port range for haproxy

    The haproxy stats and health endpoints were configured with high
    port numbers (50000 and 50936) that conflict with the range used for
    dynamic allocation of ports:
    
    $ cat /proc/sys/net/ipv4/ip_local_port_range
    32768   60999
    
    This can occasionally cause haproxy to fail if the kernel happens to
    pick one of those ports for a client connection.
    
    To avoid this, we should use ports outside the range shown above.
    This patch changes the stats endpoint to 30000, while the health
    endpoint is controlled by the MCO config and will be fixed in a
    separate commit there.
    cybertron authored and openshift-cherrypick-robot committed Feb 15, 2022
    Configuration menu
    Copy the full SHA
    22e16d7 View commit details
    Browse the repository at this point in the history