You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Disks for which their delete saga unwound prior to the fixes in #4547 would be "phantom" disks: they would be soft-deleted but would consume virtual resources and count towards quotas. If the user created a disk with the same name after attempting to delete the original disk, this new disk would prevent the phantom disk from being un-deleted due to the constraint that disk names within a project must be unique:
CREATEUNIQUE INDEXIF NOT EXISTS lookup_disk_by_project ONomicron.public.disk (
project_id,
name
) WHERE
time_deleted IS NULL;
As written today, the background task does not rename the disk, so the un-delete step would fail every time the background task is triggered.
Possible fixes:
rename the disk to something unique during un-deletion
trigger the disk delete saga instead of un-deleting the disk
The text was updated successfully, but these errors were encountered:
When un-deleting phantom disks and setting them to faulted, use a new
name that includes the disk's UUID: this ensures that even if a user
created another disk with the same name in the project, the phantom disk
can still be un-deleted and faulted, and eventually cleaned up.
Fixesoxidecomputer#4673
When un-deleting phantom disks and setting them to faulted, use a new
name that includes the disk's UUID: this ensures that even if a user
created another disk with the same name in the project, the phantom disk
can still be un-deleted and faulted, and eventually cleaned up.
Fixes#4673
Disks for which their delete saga unwound prior to the fixes in #4547 would be "phantom" disks: they would be soft-deleted but would consume virtual resources and count towards quotas. If the user created a disk with the same name after attempting to delete the original disk, this new disk would prevent the phantom disk from being un-deleted due to the constraint that disk names within a project must be unique:
As written today, the background task does not rename the disk, so the un-delete step would fail every time the background task is triggered.
Possible fixes:
The text was updated successfully, but these errors were encountered: