Skip to main content
print this page

Datalab Studio creation failure

· 2 min read
Fix Available
Fix Available
This bug has been fixed

Datalab post custom R image changes fail due to corrupted backend image corresponding to the required R configurations

Affected Versions: 3.0 3.0.3 3.0.6

Fix Version: 3.1

Root cause(s)​

A new custom R image (for R configurations) was provided for customers to use via Datalabb studios but older studios didn't have this image leading to failure in deletion of these older studios. The root cause for this is the logic checks behind the scenes for deletion also tries to find the custom R image. Fix has been made for the same, although for studios created before January, 2025(which are stuck in Deleting state), a more in-depth manual cleanup might be required.

Impact​

  • Datalabs Studios that were created before recent updates for custom R images which were to be attached to all datalabs(studios) (before January 2025), any deletion triggered afterwards cause studio being stuck in Deleting state, as the underlying domain deletion fails due to faulty error handling.
  • This is due to a check for the custom R image which is expected to be present in the studios domain configurations.

Mitigation​

Fix available

Fix is available from Amorphic version 3.0.6. Please upgrade to the aforementioned version or beyond to resolve this issue.

Timeline​

  • 2025-06-23: Bug reported/identified (CLOUD-5964)
  • 2025-06-23: Bug triaged and documented
  • 2025-06-24: Root cause analysis, fix implemented and testing completed
  • 2025-06-25: Solution merged and newer version having the fix