kubevirt: VM boot failure on ubuntu
Is this a BUG REPORT or FEATURE REQUEST?: /kind bug
What happened: When booting example/vmi-fedora.yaml on ubuntu, it failed with following error message form virt-handler
{"component":"virt-handler","level":"error","msg":"failed to create tap device named tap0","pos":"podinterface.go:488","reason":"could not retrieve pid 24447 selinux label: operation not supported","timestamp":"2021-03-01T09:51:09.923220Z"}
{"component":"virt-handler","level":"error","msg":"failed to prepare pod networking","pos":"podinterface.go:204","reason":"could not retrieve pid 24447 selinux label: operation not supported","timestamp":"2021-03-01T09:51:09.923333Z"}
{"component":"virt-handler","kind":"","level":"error","msg":"Synchronizing the VirtualMachineInstance failed.","name":"vmi-fedora","namespace":"default","pos":"vm.go:1435","reason":"failed to configure vmi network: Critical network error: could not retrieve pid 24447 selinux label: operation not supported","timestamp":"2021-03-01T09:51:09.923729Z","uid":"066dccd6-7db2-428e-b53e-6484192155a4"}
{"component":"virt-handler","level":"error","msg":"virt-launcher crashed due to a network error. Updating VMI vmi-fedora status to Failed","pos":"vm.go:933","timestamp":"2021-03-01T09:51:09.924296Z"}
{"component":"virt-handler","level":"info","msg":"re-enqueuing VirtualMachineInstance default/vmi-fedora","pos":"vm.go:1043","reason":"failed to configure vmi network: Critical network error: could not retrieve pid 24447 selinux label: operation not supported","timestamp":"2021-03-01T09:51:09.956138Z"}
What you expected to happen: VM boot successfully.
How to reproduce it (as minimally and precisely as possible):
export KUBEVIRT_PROVIDER=kind-k8s-1.17
export KUBEVIRT_NUM_NODES=2
make cluster-up
make cluster-build
make cluster-deploy
kubectl apply -f example/vmi-fedora.yaml
kubectl logs -n kubevirt virt-handler-rhcts
Anything else we need to know?: It seems related to the https://github.com/kubevirt/kubevirt/pull/4849/files. Maybe because no selinux situation is not considered.
Environment:
- KubeVirt version: 7c366278fe76a6ec5cd8acacad7a7f3debef850e
- OS (e.g. from /etc/os-release): Ubuntu 18.04.5 LTS
- Kernel (e.g.
uname -a): 5.9.0
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Reactions: 2
- Comments: 17 (9 by maintainers)
@Viste if you’re seening this again, please open a new issue and provide the data requested in the issue template.
Extremely important to know what node OS you’re using, and which KubeVirt version you’ve deployed.
I created a quick fix… for the case if this issue is blocking someone.