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

[CI] TestRouteHardStopAfterEnableOnIngressConfig update anomalies

XMLWordPrintable

    • Quality / Stability / Reliability
    • False
    • Hide

      None

      Show
      None
    • 1
    • Low
    • No
    • None
    • None
    • Rejected
    • NE Sprint 258
    • 1
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Description of problem:

      As described in https://github.com/openshift/cluster-ingress-operator/pull/1052#issuecomment-2118548732, this update from the TestRouteHardStopAfterEnableOnIngressConfig test: 

                  {
                      Name:      \"ROUTER_DISABLE_HTTP2\",
      -               Value:     \"false\",
      +               Value:     \"true\",
                      ValueFrom: nil,
                                                              },
                  {
                      Name: \"ROUTER_DISABLE_NAMESPACE_OWNERSHIP_CHECK\", Value: \"false\"},
                  {
                      Name: \"ROUTER_DOMAIN\", 
                      Value: \"apps.ci-op-tg7xmq00-76b3b.origin-ci-int-gce.dev.rhcloud.com\"},
      +               {Name: \"ROUTER_HARD_STOP_AFTER\", Value: \"3h20m0s\"},

      The "3h20m" value has to be from this update: https://github.com/openshift/cluster-ingress-operator/blob/487fe81f1a6b70e17e304b0ede0de849cb7bfac0/test/e2e/hard_stop_after_test.go#L49

      if err := hardStopAfterTestIngressConfig(t, kclient, ingressConfig, routerDeployment, (200 * time.Minute).String()); err != nil {
      

      However, TestRouteHardStopAfterEnableOnIngressConfig is a serial test, and so are TestRouteHTTP2EnableAndDisableIngressController and TestRouteHTTP2EnableAndDisableIngressConfig, so it isn't clear why a single update would modify both ROUTER_DISABLE_HTTP2 and ROUTER_HARD_STOP_AFTER.

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

          4.17

      How reproducible:

          Unknown

      Steps to Reproduce:

          1. Run test TestRouteHardStopAfterEnableOnIngressConfig
          2. Have bad luck
          3. Observe logs
          

      Actual results:

          One update modifies both ROUTER_DISABLE_HTTP2 and ROUTER_HARD_STOP_AFTER

      Expected results:

          The tests are not run in parallel so one update should not modify both values.

      Additional info:

          

              rfredett@redhat.com Ryan Fredette
              cholman@redhat.com Candace Holman
              None
              None
              Hongan Li Hongan Li
              None
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: