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

DSPO fails to successfully deploy an aws bucket configuration

XMLWordPrintable

    • 2
    • False
    • None
    • False
    • Testable
    • No
    • 1.27.0-24
    • No
    • No
    • Pending
    • None
    • ML Ops Sprint 1.27

      Description of problem:

      DSPO fails to deploy dspa when an aws s3 bucket is provided for external storage configuration. This is because we specify the default port '80', there are 2 issues with this, first for secure https connections, aws uses port 443. But, even if we specify this option it still will not work, because the minio module used upstream does not seem to work when a port is specified (even if it's 443) when connecting to aws s3. It seems to only work when there is no port specified.

      The solution is to not specify a default port 80 at all when no port in dspa is supplied.

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

      Steps to Reproduce

      1. put in aws bucket configurations and deploy a DSPA

      Actual results:

      dsp api server crashes, failing to connect to aws s3 bucket, due to incorrect port

      Expected results:

      successfull dspa deployment, with artifact storage into s3

      Reproducibility (Always/Intermittent/Only Once): always

      Build Details:

      Workaround:

       

      Workaround is to add an empty `port: ""` when specifying external storage with aws s3 store.

      Additional info:

              humairkhan Humair Khan
              humairkhan Humair Khan
              Jorge Garcia Oncins Jorge Garcia Oncins
              Votes:
              0 Vote for this issue
              Watchers:
              5 Start watching this issue

                Created:
                Updated:
                Resolved: