-
Bug
-
Resolution: Done-Errata
-
Major
-
None
-
Quality / Stability / Reliability
-
False
-
False
-
CLOSED
-
Important
-
No
+++ This bug was initially created as a clone of Bug #2038679 +++
Description of problem:
When cloning with volume mode file system, using storage API fails due to resizing.
Version-Release number of selected component (if applicable):
4.10
How reproducible:
100%
Steps to Reproduce:
1. Create DV with file system, using storage api:
apiVersion: cdi.kubevirt.io/v1alpha1
kind: DataVolume
metadata:
name: <dv name>
annotations:
cdi.kubevirt.io/storage.bind.immediate.requested: "true"
spec:
storage:
resources:
requests:
storage: 38Gi
storageClassName: hostpath-provisioner
source:
http:
url: <os image>
2. Create clone
apiVersion: cdi.kubevirt.io/v1beta1
kind: DataVolume
metadata:
name: dest-dv
spec:
source:
pvc:
name: <DV NAME>
namespace: <DV NAMESPACE>
storage:
resources:
requests:
storage: 38Gi
storageClassName: hostpath-provisioner
contentType: kubevirt
Actual results:
clone fails:
The request is invalid: spec.source.PVC: target resources requests storage size is smaller than the source
Expected results:
DV created.
Additional info:
Same clone using PVC API pass