-
Bug
-
Resolution: Duplicate
-
Undefined
-
None
-
None
-
None
-
Quality / Stability / Reliability
-
0.42
-
False
-
-
False
-
None
-
-
None
Description of problem:
Many tier-1 tests are doing VolumeSnapshot based cloning. When running the sig-storage tests on GCP cluster with 4.18.0, we found an issue in the clone populator VolumeSnapshots watch. If the snapshot wasn't Ready at the initial loop, it won't be re-queued. This is causing DataVolumes to get stuck in the CloneFromSnapshotSourceInProgress phase. It seems that in GCP it takes longer for VolumeSnapshots to become Ready, which revealed this issue.
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
1. 2. 3.
Actual results:
Expected results:
Additional info:
- duplicates
-
CNV-56518 Clone populator is stuck forever when VolumeSnapshot is not Ready
-
- Verified
-