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

[DSG] Upload Secret in workbench double encodes the values

    XMLWordPrintable

Details

    • Bug
    • Resolution: Done
    • Major
    • RHODS_1.26.0_GA
    • RHODS_1.25.0_GA
    • UI
    • False
    • None
    • False
    • Release Notes
    • Testable
    • No
    • 1.26.0
    • No
    • Hide
      == Uploading a secret file containing environment variables results in double-encoded values

      Previously, when creating a workbench in a data science project, if you uploaded a YAML-based secret file containing environment variables, the environment variable values were not decoded. Then, in the resulting OpenShift secret created by this process, the encoded values were encoded again. This issue is now fixed.
      Show
      == Uploading a secret file containing environment variables results in double-encoded values Previously, when creating a workbench in a data science project, if you uploaded a YAML-based secret file containing environment variables, the environment variable values were not decoded. Then, in the resulting OpenShift secret created by this process, the encoded values were encoded again. This issue is now fixed.
    • Bug Fix
    • Done
    • No
    • Yes
    • None
    • RHODS 1.26

    Description

      Description of problem:

      when you upload a secret yaml file, the values do not get decoded before storing them into the Secret. It means, the values get re-encoded. If you add a new environment variable in the workbench using the Key/Value method, it doesn't happen.

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

      Steps to Reproduce

      1. create a DS project
      2. create a workbench and add env variables by uploading a Secret (yaml format)
      3. fill the remaining workbench data
      4. submit the workbench creation
      5. check the Secret which gets created in OpenShift

      Actual results:

      values under "data" section of the Secret get encoded twice: the yaml file has already the values encoded

      Expected results:

      values under "data" section of the Secret do not get re-encoded

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      RHODS 1.25

      Workaround:

      decode the values when using the environment variables in Jupyter

      Additional info:

      Attachments

        Issue Links

          is caused by

          Bug - A problem that impairs or prevents the functions of the product. RHODS-5932 [DSG] missing upload option for creating an environment variable as Secret

          • Normal - To be worked after urgent and high priorities are resolved. This term is chosen when the severity of an issue is relatively close to the level of effort to fix it. The existence of an easily implemented workaround can also lead to this priority level instead of a higher priority.
          • Closed
          mentioned on

          GitLab Merge request - Updated 5 upstream sources

          GitLab Merge request - Updated US source to: f7c1b37 Merge pull request #272 from red-hat-data-services/main

          Activity

            People

              Unassigned Unassigned
              rhn-support-bdattoma Berto D'Attoma
              Berto D'Attoma Berto D'Attoma
              Votes:
              0 Vote for this issue
              Watchers:
              6 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: