Uploaded image for project: 'Red Hat OpenShift Data Science'
  1. Red Hat OpenShift Data Science
  2. RHODS-4366

Idle Culler value is getting reset to "do not stop idle notebooks". a lot.

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Yes
    • No
    • Hide
      Cluster settings were reset on operator restart:: When the OpenShift Data Science operator pod was restarted, cluster settings were sometimes reset to their default values, removing any custom configuration. The OpenShift Data Science operator was restarted when a new version of OpenShift Data Science was released, and when the node running the operator failed. This issue occurred because the operator deployed ConfigMaps incorrectly. Operator deployment instructions have been updated so that this no longer occurs.

      Show
      Cluster settings were reset on operator restart:: When the OpenShift Data Science operator pod was restarted, cluster settings were sometimes reset to their default values, removing any custom configuration. The OpenShift Data Science operator was restarted when a new version of OpenShift Data Science was released, and when the node running the operator failed. This issue occurred because the operator deployed ConfigMaps incorrectly. Operator deployment instructions have been updated so that this no longer occurs.
    • Documented as Resolved Issue
    • No
    • Yes
    • None
    • RHODS 1.14

      Description of problem:

      I had chosen to setup the idle culler to cull notebooks after 2H. 

      Today, after the update to the latest version of RHODS, it's been reset to "do not stop idle notebooks". 

      Prerequisites (if any, like setup, operators/versions):

      Steps to Reproduce

      1. wait for an update

      Actual results:

      it's reset to "not stop idle notebook". 

      Expected results:

      It would remember my choice. 

      Reproducibility (Always/Intermittent/Only Once):

      Always. I had seen this before but I was not sure. This morning following the version update to 1.12, i can see this in 3 distinct production environments. 

      Build Details:

      Workaround:

      Additional info:

        1. image-2022-06-27-08-53-09-552.png
          image-2022-06-27-08-53-09-552.png
          39 kB
        2. image-2022-06-27-08-55-45-040.png
          image-2022-06-27-08-55-45-040.png
          50 kB
        3. image-2022-07-22-10-32-49-690.png
          image-2022-07-22-10-32-49-690.png
          24 kB

              rh-ee-mroman Maros Roman (Inactive)
              egranger@redhat.com Erwan Granger
              Milind Waykole Milind Waykole
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: