-
Bug
-
Resolution: Done-Errata
-
Critical
-
CNV v4.15.7
-
None
-
Incidents & Support
-
0.42
-
False
-
-
False
-
None
-
-
Storage Core Sprint 262
-
Important
-
None
Description of problem:
Some importer logs send a "no new block" message like the one below and this data transfer is not completed. "No new block status data at offset"
Version-Release number of selected component (if applicable):
4.15
How reproducible:
100%
Steps to Reproduce:
1. Import 2G+ VMWare disk 2. 3.
Actual results:
"No new block status data at offset" error in logs
Expected results:
Import finishes successfully
Additional info:
- is cloned by
-
CNV-50394 [4.16] VDDK Import Error: No new block status data at offset
-
- Closed
-
- is depended on by
-
MTV-1629 TestOnly: VMware warm migration stuck: "No new block status data at offset 6806175744"
-
- Closed
-
- links to
-
RHEA-2024:138842 OpenShift Virtualization 4.15.7 Images
- mentioned on