Uploaded image for project: 'Web Terminal for OpenShift'
  1. Web Terminal for OpenShift
  2. WTO-132

Custom idling timeout does not affect on the terminal with DWO 0.15.2

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Not a Bug
    • Icon: Major Major
    • None
    • 1.5.0
    • operator
    • None
    • False
    • None
    • False
    • Hide
      • Prepare a cluster and setm DWO operator v. 0.15.2 using IIB images:
      • Index image v4.10: registry-proxy.engineering.redhat.com/rh-osbs/iib:269803
      • Index image v4.11: registry-proxy.engineering.redhat.com/rh-osbs/iib:269804
      • Setup WebTerminal (we can use OLM)
      • Apply idling timeout:
      cat <<EOF | oc apply -f -
      apiVersion: controller.devfile.io/v1alpha1
      kind: DevWorkspaceOperatorConfig
      metadata:
        name: devworkspace-operator-config
        namespace: openshift-operators
      config:
        workspace:
          idleTimeout: 60s
      EOF
      
      
      • Wait 60sec.
        *Expected result:* The WebTerminal should be stopped after 1 minute
        *Actual result:* The WebTerminal's just stopped by default timeout
      Show
      Prepare a cluster and setm DWO operator v. 0.15.2 using IIB images: Index image v4.10: registry-proxy.engineering.redhat.com/rh-osbs/iib:269803 Index image v4.11: registry-proxy.engineering.redhat.com/rh-osbs/iib:269804 Setup WebTerminal (we can use OLM) Apply idling timeout: cat <<EOF | oc apply -f - apiVersion: controller.devfile.io/v1alpha1 kind: DevWorkspaceOperatorConfig metadata:   name: devworkspace-operator-config   namespace: openshift-operators config:   workspace:     idleTimeout: 60s EOF Wait 60sec. * Expected result: * The WebTerminal should be stopped after 1 minute * Actual result: * The WebTerminal's just stopped by default timeout

      Seems DWO ignores custom idling timeout (60s), 

              ibuziuk@redhat.com Ilya Buziuk
              mmusiien Maksym Musienko
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: