-
Bug
-
Resolution: Duplicate
-
Normal
-
CNV v4.18.13
-
None
-
Quality / Stability / Reliability
-
False
-
-
False
-
None
-
-
None
Description of problem:
Upload a video to show the problem.
Version-Release number of selected component (if applicable):
CNV 4.18.11(latest stable version for now)
How reproducible:
Always
Steps to Reproduce:
1. The VM's volumes should be dataVolume like below by default:
$ oc get vm rhel8-testing -o yaml|yq .spec.template.spec.volumes
- dataVolume:
name: rhel8-testing
name: rootdisk
2. VirtualMachines --> VM --> Configuration --> Storage
3. Bootable/ addition disk --> Edit --> PVC size
4. Expanding the disk size, and then it will map to another pvc which create automatically, names like dv-{VM-name}-{disk-name}-XXXX
Actual results:
The disk `Source` is changed to another pvc which create automatically, names like dv-{VM-name}-{disk-name}-XXXX
Expected results:
The disk(pvc) should be expanded normally, and `Source` should not be changed.
Additional info:
1. The more negative impact is, if stop the VM and start the VM again, it will use that wrong disk with that wrong PVC!
2. The workaround is to expand the PVC in:
Storage => PVC => Expand PVC
3. If the VM's .spec.template.spec.volumes is PVC, not the data volume, like below:
- name: disk-ivory-guanaco-42
persistentVolumeClaim:
claimName: rhel8-disk2
It won't meet this issue. but the dv(data volume) in kubevirt seemed like the recommended way.
- duplicates
-
-
- Verified
-
