Source PVC's deletion make VolumeSnapshot broken
- Dominant language
- Go
- Stars
- 515
- Forks
- 88
- PR merge metrics
- No merged PRs in 30d
Description
### Ⅰ. Issue Description
1. create VolumeSnapshot From PVC
2. delete PVC
3. VolumeSnapshot is broken, can not be use, got Log:
```
[ProcessSnapshotPVC] get src pvc ns/[VolumeSnapshot] failed: persistentvolumeclaim [source PVC] not found
```
### Ⅱ. Describe what happened
### Ⅲ. Describe what you expected to happen
protect VolumeSnapshot source PVC from deletion with finalizer
### Ⅳ. How to reproduce it (as minimally and precisely as possible)
### Ⅴ. Anything else we need to know?
### Ⅵ. Environment:
- Open-Local version:
- OS (e.g. from /etc/os-release):
- Kernel (e.g. `uname -a`):
- Install tools:
- Others:
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the VolumeSnapshot and PVC lifecycle described in the issue, then trace the ProcessSnapshotPVC path associated with the reported source-PVC-not-found log. Reproduce the three-step sequence and verify that deleting the source PVC no longer leaves the VolumeSnapshot unusable because the source PVC is protected by a finalizer.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100