Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-60257

indentation issue of "frontend public" in haproxy

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • None
    • None
    • Rejected
    • NI&D Sprint 277
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      In haproxy.conf, there are some space charaters before "frontend public"

      Version-Release number of selected component (if applicable):

          4.20.0-0.nightly-2025-07-31-063120(4.18 nightly build also had the issue)

      How reproducible:

          100%

      Steps to Reproduce:

          1.rsh to a router pod
      
          2.check the haproxy.conf, for the "  frontend public", there are two spaces before "frontend public", which should be removed.
      
      defaults
        maxconn 50000
      
      
        # To configure custom default errors, you can either uncomment the
        # line below (server ... 127.0.0.1:8080) and point it to your custom
        # backend service or alternatively, you can send a custom 503 or 404 error.
        #
        # server openshift_backend 127.0.0.1:8080
        errorfile 503 /var/lib/haproxy/conf/error-page-503.http
        errorfile 404 /var/lib/haproxy/conf/error-page-404.http
      
      
        timeout connect 5s
        timeout client 30s
        timeout client-fin 1s
        timeout server 30s
        timeout server-fin 1s
        timeout http-request 10s
        timeout http-keep-alive 300s
      
      
        # Long timeout for WebSocket connections.
        timeout tunnel 1h
      
      
        # Prevent failures at startup due to name resolution
        default-server init-addr last,none resolvers ingress_dns
      
      
      # Define a resolver to be used when servers are specified by name and
      # therefore requires name resolution. Server name resolution typically
      # occurs only at startup. With this configuration, name resolution
      # will occur once every 10s. Successful name resolution results in the
      # server being marked UP while failure results in the server being
      # marked DOWN. Note this only occurs when servers are specified by
      # name.
      resolvers ingress_dns
        parse-resolv-conf
        resolve_retries 1
        timeout retry 5s
        timeout resolve 10s
      
      
      
      
      
      
        frontend public
      
      
        bind :80 accept-proxy
        mode http     
      
      3. 4.12 - 4.19 builds should have such issue
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

              btofelrh Brett Tofel
              shudili@redhat.com Shudi Li
              None
              None
              Shudi Li Shudi Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              8 Start watching this issue

                Created:
                Updated: