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

Setting haproxy.router.openshift.io/timeout=99999999s on route causes ingress controller to fail

    XMLWordPrintable

Details

    • Critical
    • No
    • 1
    • Sprint 236
    • 1
    • Rejected
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

       

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

       

      How reproducible:

       

      Steps to Reproduce:

      1. Create test route 
      2. oc annotate route test --overwrite haproxy.router.openshift.io/timeout=99999999999999999s
      3. Restart ingress pods

      Actual results:

      Ingress goes into crashloopbackoff
      
      Logs: 
      
      [ALERT] 132/170130 (382) : parsing [/var/lib/haproxy/conf/haproxy.config:245] : timer overflow in argument '99999999999999999s' to 'timeout server' (maximum value is 2147483647 ms or ~24.8 days)
      [ALERT] 132/170130 (382) : Error(s) found in configuration file : /var/lib/haproxy/conf/haproxy.config
      [ALERT] 132/170130 (382) : Fatal errors found in configuration.
      

      Expected results:

      Route should fail validation and not get accepted. 

      Additional info:

      This dev operation should not bring down ingress for the WHOLE cluster. 

      Attachments

        Activity

          People

            mmasters1@redhat.com Miciah Masters
            rhn-support-rhowe Ryan Howe
            Shudi Li Shudi Li
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: