-
Bug
-
Resolution: Done-Errata
-
Critical
-
MTC 1.8.7
-
None
Description of problem:
Virt-launcher pod keeps in pending after migrate the vm from hostpath-csi-basic to hostpath-csi-pvc-block
Version-Release number of selected component (if applicable):
CNV-v4.19.0.rhel9-154, MTC 1.8.7-8
How reproducible:
4/5
Steps to Reproduce:
1. Create a VM with hostpath-csi-basic SC 2. Create a migplan migrate the SC to hostpath-csi-pvc-block 3. Start the storage class migration
Actual results:
Virt-launcher pod keeps in pending after migrate the vm from hostpath-csi-basic to hostpath-csi-pvc-block $ oc get pod -n mig1 NAME READY STATUS RESTARTS AGE virt-launcher-centos10a-995xc 2/2 Running 0 23m virt-launcher-centos10a-b8jr9 0/2 Pending 0 3m32s Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 3m52s default-scheduler 0/6 nodes are available: 1 node(s) didn't match pod anti-affinity rules, 2 node(s) had volume node affinity conflict, 3 node(s) had untolerated taint {node-role.kubernetes.io/master: }. preemption: 0/6 nodes are available: 1 No preemption victims found for incoming pod, 5 Preemption is not helpful for scheduling.
Seems the pod anti affinity is what prevents the pod being scheduled on the same node as the running VM. And the volume got bound to the same node as the source.
- links to
-
RHBA-2025:151265 Migration Toolkit for Containers (MTC) 1.8.9 security and bug fix update