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

Downtime of almost 30min of pytorch and tensor flow builds during catalog source upgrade

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • None
    • RHODS_1.4.0_GA
    • Workbenches
    • 1
    • False
    • False
    • No
    • Yes
    • Hide
      == PyTorch and TensorFlow images were unavailable when upgrading
      When upgrading from OpenShift Data Science 1.3 to a later version, PyTorch and TensorFlow images were unavailable to users for approximately 30 minutes. As a result, users were unable to start PyTorch and TensorFlow notebooks in Jupyter during the upgrade process. This issue has now been resolved.
      Show
      == PyTorch and TensorFlow images were unavailable when upgrading When upgrading from OpenShift Data Science 1.3 to a later version, PyTorch and TensorFlow images were unavailable to users for approximately 30 minutes. As a result, users were unable to start PyTorch and TensorFlow notebooks in Jupyter during the upgrade process. This issue has now been resolved.
    • Bug Fix
    • Done
    • No
    • Yes
    • None
    • MODH Sprint 36, MODH Sprint 37
    • Important

      Description of problem:

      During the RHODS upgrade from v1.3.0-6 to v1.4.0-2 we observed that builds are getting recreated during the upgrade and it take almost 30mins for pytorch and tensor flow builds to up and running

      Note:

      1. In this time user can not Launch the pytorch and tensor flow notebook from JH (select buttons are disabled)
      2. If notebooks (pytoch/tensorflow) are already launch prior to upgrade it will work without any problem

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

      Steps to Reproduce

      1. Perform RHODS upgrade

      Actual results:

      During the upgrade user can not launch pytorch and tensorflow notebook

      Expected results:

      User should able to Launch all the notebooks images during the upgrade as per the choice. There should not be any disruption in the serviceĀ 

      Reproducibility (Always/Intermittent/Only Once):

      Always

      Build Details:

      Workaround:

      Additional info:

        1. 117_118_upgrade.png
          117_118_upgrade.png
          83 kB
        2. Generic_notebook_IS.png
          Generic_notebook_IS.png
          96 kB
        3. pytorch_notebook_IS.png
          pytorch_notebook_IS.png
          45 kB
        4. Screenshot from 2021-12-17 17-58-56.png
          Screenshot from 2021-12-17 17-58-56.png
          28 kB
        5. Screenshot from 2021-12-17 18-01-26.png
          Screenshot from 2021-12-17 18-01-26.png
          59 kB
        6. Screenshot from 2021-12-17 21-42-04.png
          Screenshot from 2021-12-17 21-42-04.png
          33 kB
        7. upgrade.png
          upgrade.png
          25 kB

              svelosol@redhat.com Samuel Veloso (Inactive)
              takumar@redhat.com Tarun Kumar
              Tarun Kumar Tarun Kumar
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: