kubevirt: Kind: Readiness probe failed: cat: /var/run/kubevirt-infra/healthy: No such file or directory
Is this a BUG REPORT or FEATURE REQUEST?:
Uncomment only one, leave it on its own line:
/kind bug
/kind enhancement
What happened: after ‘make cluster-sync’, I have
root@jj-virt:~/go/src/github.com/kubevirt/kubevirt# ./cluster-up/kubectl.sh get pods --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
cdi cdi-apiserver-669594d5d6-46ppd 1/1 Running 0 51s
cdi cdi-deployment-78548d9b85-vhd2j 1/1 Running 0 50s
cdi cdi-operator-6b7757ccf7-cbm4c 1/1 Running 0 55s
cdi cdi-uploadproxy-6b9c645fc8-vlw9k 1/1 Running 0 51s
kube-system coredns-fb8b8dccf-dxt2d 1/1 Running 0 46m
kube-system coredns-fb8b8dccf-zhjf2 1/1 Running 0 46m
kube-system etcd-kind-1.14.2-control-plane 1/1 Running 0 45m
kube-system kube-apiserver-kind-1.14.2-control-plane 1/1 Running 0 46m
kube-system kube-controller-manager-kind-1.14.2-control-plane 1/1 Running 1 46m
kube-system kube-flannel-ds-amd64-n2t7c 1/1 Running 0 46m
kube-system kube-proxy-6kwtx 1/1 Running 0 46m
kube-system kube-scheduler-kind-1.14.2-control-plane 1/1 Running 1 46m
kubevirt cdi-http-import-server-67f465c78b-7zvk4 1/1 Running 0 54s
kubevirt virt-api-768945d6c-87f5h 1/1 Running 0 47s
kubevirt virt-api-768945d6c-znzbc 1/1 Running 0 47s
kubevirt virt-controller-7545944d75-l2997 1/1 Running 0 28s
kubevirt virt-controller-7545944d75-ps2cv 1/1 Running 0 28s
kubevirt virt-handler-hv5xt 1/1 Running 0 28s
kubevirt virt-operator-5d59f6cbff-4hlv4 1/1 Running 0 54s
kubevirt virt-operator-5d59f6cbff-s2wnj 1/1 Running 0 54s
and
wget https://raw.githubusercontent.com/kubevirt/kubevirt.github.io/master/labs/manifests/vm.yaml
./cluster-up/kubectl.sh create -f ~/vm.yaml
# ./cluster-up/virtctl.sh start testvm
VM testvm was scheduled to start
default virt-launcher-testvm-cn9hp 1/2 Running 0 11s
Type Reason Age From Message
---- ------ ---- ---- -------
Normal Scheduled 18s default-scheduler Successfully assigned default/virt-launcher-testvm-xbtv2 to kind-1.14.2-control-plane
Normal Pulling 18s kubelet, kind-1.14.2-control-plane Pulling image "kubevirt/cirros-registry-disk-demo"
Normal Pulled 17s kubelet, kind-1.14.2-control-plane Successfully pulled image "kubevirt/cirros-registry-disk-demo"
Normal Created 16s kubelet, kind-1.14.2-control-plane Created container volumecontainerdisk
Normal Started 16s kubelet, kind-1.14.2-control-plane Started container volumecontainerdisk
Normal Pulled 16s kubelet, kind-1.14.2-control-plane Container image "localhost:5000/kubevirt/virt-launcher@sha256:1ce1fc516a912e5cf00ed63d36cb0e9ef60fae254099b2ce1440aff9d798db81" already present on machine
Normal Created 16s kubelet, kind-1.14.2-control-plane Created container compute
Normal Started 16s kubelet, kind-1.14.2-control-plane Started container compute
Warning Unhealthy 1s (x11 over 11s) kubelet, kind-1.14.2-control-plane Readiness probe failed: cat: /var/run/kubevirt-infra/healthy: No such file or directory
Warning Unhealthy 1s kubelet, kind-1.14.2-control-plane Readiness probe errored: rpc error: code = Unknown desc = failed to exec in container: container is in CONTAINER_EXITED state
What you expected to happen:
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
Environment:
- KubeVirt version (use
virtctl version): - Kubernetes version (use
kubectl version): - VM or VMI specifications:
- Cloud provider or hardware configuration:
- OS (e.g. from /etc/os-release):
- Kernel (e.g.
uname -a): - Install tools:
- Others:
About this issue
- Original URL
- State: closed
- Created 5 years ago
- Reactions: 1
- Comments: 18 (17 by maintainers)
Interesting but a good reminder to add a migration testcase to the demo repository and kind branch