What happened:
A clear and concise description of what the bug is.
networks use default pod, interfaces mode use bridge. When I successfully created the VMs and then deleted and recreated them, the VMs could not obtain the IP address
What you expected to happen:
A clear and concise description of what you expected to happen.
When I delete and then recreate the VMs, I can obtain the IP address
How to reproduce it (as minimally and precisely as possible):
Steps to reproduce the behavior.
After creating the VMs according to the above file, delete the VMs and then recreate them
Additional context:
Add any other context about the problem here.
kubevirt: 1.2.0
kubernetes: 1.27.16
cni:(I tried using both, but neither of them worked)
calico: 3.25.0
cilium: 1.15.8
Environment:
KubeVirt version (use virtctl version): N/A
Kubernetes version (use kubectl version): N/A
VM or VMI specifications: N/A
Cloud provider or hardware configuration: N/A
OS (e.g. from /etc/os-release): Debian GNU/Linux 12 (bookworm)
What happened: A clear and concise description of what the bug is. networks use default pod, interfaces mode use bridge. When I successfully created the VMs and then deleted and recreated them, the VMs could not obtain the IP address
What you expected to happen: A clear and concise description of what you expected to happen. When I delete and then recreate the VMs, I can obtain the IP address
How to reproduce it (as minimally and precisely as possible): Steps to reproduce the behavior.
After creating the VMs according to the above file, delete the VMs and then recreate them
Additional context: Add any other context about the problem here. kubevirt: 1.2.0 kubernetes: 1.27.16 cni:(I tried using both, but neither of them worked) calico: 3.25.0 cilium: 1.15.8
Environment:
virtctl version
): N/Akubectl version
): N/Auname -a
): 6.1.0-23-amd64