Lab: LiveMigration out of date

[aburdenthehand]

What happened:
A user on kubevirt-dev mailing list hit upon a problem with this lab; I'm filing this on their behalf. Looking at the lab, the docs are out of date.

User comments:
I reated the Vm as indicated

[root@kubemaster-ot test1]# kubectl get vm,vmi,pods
NAME                                AGE    STATUS    READY
[virtualmachine.kubevirt.io/testvm](http://virtualmachine.kubevirt.io/testvm)   5m3s   Running   True

NAME                                        AGE     PHASE     IP            NODENAME        READY
[virtualmachineinstance.kubevirt.io/testvm](http://virtualmachineinstance.kubevirt.io/testvm)   4m51s   Running   10.244.2.96   kubeclient-ot   True

NAME                             READY   STATUS    RESTARTS   AGE
pod/virt-launcher-testvm-chttc   0/3     Pending   0          60s
pod/virt-launcher-testvm-wdd5t   3/3     Running   0          4m50s

The command virtctk migrate start but stay in pending.
No log is produced.

[root@kubemaster-ot test1]#
[root@kubemaster-ot test1]# kubectl logs pod/virt-launcher-testvm-chttc
[root@kubemaster-ot test1]#

I'm using containerd as anvironment.
I will try with dokerd.

Additional context:
https://kubevirt.io/labs/kubernetes/migration.html

Now that we're on a slower release cadence, we should be able to update these labs on an annual basis, tied to the most recently released version, which will be supported for ~12 months. Running and updating the labs could be a useful exercise for new contributors, provided they are supported if and when they need to troubleshoot changes in the procedure.

Github link: https://github.com/kubevirt/kubevirt.github.io/blob/main/labs/kubernetes/migration.md

[kubevirt-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[kubevirt-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

[kubevirt-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

[kubevirt-bot]

@kubevirt-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[aburdenthehand]

/remove-lifecycle rotten