-
Bug
-
Resolution: Unresolved
-
Major
-
4.14.0
-
Quality / Stability / Reliability
-
True
-
-
None
-
Critical
-
No
-
None
-
None
-
Rejected
-
None
-
None
-
None
-
None
-
None
-
None
-
None
-
None
Description of problem:
Baremetal Kubevirt Hypershift failed with live migration
Version-Release number of selected component (if applicable):
4.14.0-0.ci-2023-09-12-113607
How reproducible:
Steps to Reproduce:
1. Build 4.14 Baremetal Kubevirt Hypershift cluster with dataVolumeAccessMode in ReadWriteMany mode
2. select a VMI to perform live migration
$ oc get vmi -A
NAMESPACE
NAME AGE PHASE IP
NODENAME READY
clusters-9828b42b78cacf30818e
9828b42b78cacf30818e-99e210a8-4j74g 94m Running 10.130.2.40
worker-3 True
clusters-9828b42b78cacf30818e
9828b42b78cacf30818e-99e210a8-hfr7r 91m Running 10.128.2.37
worker-2 True
clusters-9828b42b78cacf30818e
9828b42b78cacf30818e-99e210a8-pxjnl 94m Running 10.129.2.43
worker-1 True
$ cat migration-job.yaml
apiVersion:
kubevirt.io/v1
kind:
VirtualMachineInstanceMigration
metadata:
name:
migration-job
namespace:
clusters-9828b42b78cacf30818e
spec:
vmiName:
9828b42b78cacf30818e-99e210a8-4j74g
$ oc apply -f ./SDN-3732-kubevirt-migration/migration-job.yaml
virtualmachineinstancemigration.kubevirt.io/migration-job
created
3. check live migration status
$ oc get VirtualMachineInstanceMigration -n
clusters-9828b42b78cacf30818e
NAME
PHASE VMI
migration-job
Failed 9828b42b78cacf30818e-99e210a8-4j74g
Actual results:
live migration failed
Expected results:
live migration should success
Additional info:
- relates to
-
-
- Closed
-