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

[DSG] Workbenches restarts even when S3 data connection fails to be created

XMLWordPrintable

    • False
    • None
    • False
    • Release Notes
    • Testable
    • No
    • 1.23.0
    • No
    • Hide
      == A workbench's data connection was incorrectly updated when creating a duplicated data connection
      When creating a data connection that contained the same name as an existing data connection, the data connection creation failed, but the associated workbench still restarted and connected to the wrong data connection. This issue has been resolved. Workbenches now connect to the correct data connection.
      Show
      == A workbench's data connection was incorrectly updated when creating a duplicated data connection When creating a data connection that contained the same name as an existing data connection, the data connection creation failed, but the associated workbench still restarted and connected to the wrong data connection. This issue has been resolved. Workbenches now connect to the correct data connection.
    • Bug Fix
    • No
    • Pending
    • None
    • RHODS 1.23
    • Medium

      Description of problem:

      the scenario is the following:

      1. user creates a S3 data connection "aws-connection"
      2. user creates a workbench "workbench-test"
      3. user creates another S3 dc and connect it to "workbench-test". By mistake user assignes "aws-connection" as name (i.e., duplicate)

      After step 3, "workbench-test" gets unexpected restarted and the first S3 DC gets connected to that workbench.

      The GIF shows the scenario:

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

      Steps to Reproduce

      1. user creates a S3 data connection "aws-connection"
      2. user creates a workbench "workbench-test"
      3. user creates another S3 dc and connect it to "workbench-test". By mistake user assignes "aws-connection" as name (i.e., duplicate)
      4. check the status of the workbench and its pod
      5. check which S3 dc got connected to the workbench

      Actual results:

      although the data connection creation failed, the workbench gets restarted and connected to the wrong data connection

      Expected results:

      failure in data connection does not trigger any workbench update

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      RHODS v1.21.0-20

      Workaround:

      N/A

      Additional info:

      the scenario may become more frequent when there are many  data connections

            gkrumbac Gage Krumbach
            rhn-support-bdattoma Berto D'Attoma
            Berto D'Attoma Berto D'Attoma
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

              Created:
              Updated:
              Resolved: