(CAT-2014) Address GCP disk orphaning issue#376
Merged
david22swan merged 1 commit intomainfrom Mar 18, 2026
Merged
Conversation
A few months ago, we noticed a problem with our GCP disk management. Every few months, we would find orphaned disks with no clear owner. After some recent log digging, we traced the problem back to this LVM and its CI 'after' suite logic. The logic seems to be fragile enough to fail to properly clean up disks if the connection is momentarily lost, which seems to happen at least once every two or three months. This commit aims to make the system more robust against this issues by implementing retry logic and proper error handling.
LukasAud
force-pushed
the
CAT-2014-Address_GCP_disk_orphaning_issue
branch
from
83ce831 to
1cb7c3d
Compare
david22swan
approved these changes
Mar 18, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
A few months ago, we noticed a problem with our GCP disk management. Every
few months, we would find orphaned disks with no clear owner. After some
recent log digging, we traced the problem back to this LVM and its CI
'after' suite logic. The logic seems to be fragile enough to fail to
properly clean up disks if the connection is momentarily lost, which seems
to happen at least once every two or three months.
This commit aims to make the system more robust against this issues by
implementing retry logic and proper error handling.
Checklist