Skip to content

Instantly share code, notes, and snippets.

@j-griffith
Last active March 7, 2019 15:26
Show Gist options
  • Select an option

  • Save j-griffith/ff887a8fe85fcead3a9de48b314d4ba2 to your computer and use it in GitHub Desktop.

Select an option

Save j-griffith/ff887a8fe85fcead3a9de48b314d4ba2 to your computer and use it in GitHub Desktop.
Networks:
Name: default
Pod:
Volumes:
Data Volume:
Name: alpine-dv
Name: datavolumedisk1
Status:
Conditions:
Last Probe Time: <nil>
Last Transition Time: <nil>
Status: True
Type: LiveMigratable
Last Probe Time: <nil>
Last Transition Time: 2019-03-07T15:18:20Z
Status: True
Type: Ready
Interfaces:
Ip Address: 10.244.1.43
Mac: 0a:58:0a:f4:01:2b
Name: default
Migration Method: BlockMigration
Migration State:
Migration UID: 7e96feda-40ec-11e9-bde3-fa163e4aaadf
Source Node: kube-2.novalocal
Start Timestamp: 2019-03-07T15:21:50Z
Target Direct Migration Node Ports:
34151: 0
36889: 49152
37659: 49153
Target Node: kube-3.novalocal
Target Node Address: 10.244.2.37
Target Node Domain Detected: true
Target Pod: virt-launcher-vm-alpine-datavolume-hg5jl
Node Name: kube-2.novalocal
Phase: Running
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal SuccessfulCreate 6m48s virtualmachine-controller Created virtual machine pod virt-launcher-vm-alpine-datavolume-2wxkl
Normal Started 5m2s virt-handler, kube-2.novalocal VirtualMachineInstance started.
Normal Created 93s (x5 over 5m2s) virt-handler, kube-2.novalocal VirtualMachineInstance defined.
Normal PreparingTarget 92s virt-handler, kube-3.novalocal Migration Target is listening at 10.244.2.37, on ports: 37659,34151,36889
Normal PreparingTarget 90s (x10 over 92s) virt-handler, kube-3.novalocal VirtualMachineInstance Migration Target Prepared.
Normal Migrating 90s (x5 over 92s) virt-handler, kube-2.novalocal VirtualMachineInstance is migrating.
----------------------------------------
- launcher pod on the new/dest node (node-3)
------------------------------------------
Readiness: exec [cat /var/run/kubevirt-infra/healthy] delay=2s timeout=5s period=2s #success=1 #failure=5
Environment: <none>
Mounts:
/var/run/kubevirt from virt-share-dir (rw)
/var/run/kubevirt-ephemeral-disks from ephemeral-disks (rw)
/var/run/kubevirt-infra from infra-ready-mount (rw)
/var/run/kubevirt-private/vmi-disks/datavolumedisk1 from datavolumedisk1 (rw)
/var/run/libvirt from libvirt-runtime (rw)
Conditions:
Type Status
Initialized True
Ready True
ContainersReady True
PodScheduled True
Volumes:
datavolumedisk1:
Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
ClaimName: alpine-dv
ReadOnly: false
infra-ready-mount:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
virt-share-dir:
Type: HostPath (bare host directory volume)
Path: /var/run/kubevirt
HostPathType:
libvirt-runtime:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
ephemeral-disks:
Type: EmptyDir (a temporary directory that shares a pod's lifetime)
Medium:
QoS Class: Burstable
Node-Selectors: kubevirt.io/schedulable=true
Tolerations: node.kubernetes.io/not-ready:NoExecute for 300s
node.kubernetes.io/unreachable:NoExecute for 300s
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 4m14s default-scheduler Successfully assigned default/virt-launcher-vm-alpine-datavolume-hg5jl to kube-3.novalocal
Normal SuccessfulAttachVolume 4m14s attachdetach-controller AttachVolume.Attach succeeded for volume "pvc-b43d4947-40eb-11e9-bde3-fa163e4aaadf"
Normal Pulling 4m12s kubelet, kube-3.novalocal pulling image "index.docker.io/jgriffith/virt-launcher:devel"
Normal Pulled 2m43s kubelet, kube-3.novalocal Successfully pulled image "index.docker.io/jgriffith/virt-launcher:devel"
Normal Created 2m40s kubelet, kube-3.novalocal Created container
Normal Started 2m40s kubelet, kube-3.novalocal Started container
Warning Unhealthy 2m36s (x2 over 2m38s) kubelet, kube-3.novalocal Readiness probe failed: cat: /var/run/kubevirt-infra/healthy: No such file or directory
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment