Persistent Disk not attaching to new Cloud Environments Completed

April 21, 2022 14:26
3 comments

Some users have reported instances of creating new Cloud Environments and not being able to access their already existing Persistent Disks. The Cloud Environments start as if they have a new Persistent Disk. However, from the Cloud Environments page, the original disk can still be found.

Our engineering teams are aware of the issue and currently investigating.

Comments

3 comments

Josh Evans
- Edited May 02, 2022 15:34
- Official comment
Our engineering teams have deployed a fix for the issue. Any affected users can now resolve the issue for themselves by following these steps:
1. From the Cloud Environments page, please verify that you only have one Persistent Disk for your workspace. If you have more than one, please contact us before moving forward.
2. After you've confirmed the above, you may create a new Cloud Environment if you don't have one running already. This should attach your existing Persistent Disk.
3. If you do have a Cloud Environment that is already running on is paused. My suggestion would be to delete it. Please make sure to select the option to delete Just the Cloud Environment and not the Persistent Disk. After that, you should be able to create a new Cloud Environment and resolve the issue.
After the new Cloud Environment is running, you should be able to access your data as normal.
Mark Godek
- July 08, 2022 18:33
Hi Josh, is there any updates on this bug?

One of the users in my lab is experiencing this issue. They deleted the cloud environment and newly created PD, confirmed that there was only one PD present, and when a new cloud environment was spun up, it created another new PD rather than attaching the existing one.

0
Jason Cerrato
- July 08, 2022 19:20
Hey Mark Godek,

Thanks for letting us know about this issue. We'll follow up with you directly to get this resolved!

Kind regards,

Jason

0

Please sign in to leave a comment.