kubevirt: DHCP server6 painc error
What happened: A clear and concise description of what the bug is. virt-launcher panic
What you expected to happen: A clear and concise description of what you expected to happen.
After I created the virtual machine, restarted the vm, looked at the log of virt-lanuncher, and found the phenomenon of panic
How to reproduce it (as minimally and precisely as possible): Steps to reproduce the behavior. Occasionally
Additional context: Add any other context about the problem here. pkg/network/dhcp/serverv6/serverv6.go
func (h *DHCPv6Handler) ServeDHCPv6(conn net.PacketConn, peer net.Addr, m dhcpv6.DHCPv6) {
log.Log.V(4).Info("DHCPv6 serving a new request")
// TODO if we extend the server to support bridge binding, we need to filter out non-vm requests
response, err := h.buildResponse(m)
if err != nil {
log.Log.V(4).Reason(err).Error("DHCPv6 failed building a response to the client")
}
if _, err := conn.WriteTo(response.ToBytes(), peer); err != nil {
log.Log.V(4).Reason(err).Error("DHCPv6 failed sending a response to the client")
}
}
if response, err := h.buildResponse(m),has error will panic in this placeļ¼conn.WriteTo(response.ToBytes(), peer);
Environment:
- KubeVirt version (use
virtctl version): 0.46 - Kubernetes version (use
kubectl version): 1.23 - VM or VMI specifications: N/A
- Cloud provider or hardware configuration: N/A
- OS (e.g. from /etc/os-release): Centos7.6
- Kernel (e.g.
uname -a): N/A - Install tools: N/A
- Others: N/A
About this issue
- Original URL
- State: closed
- Created 2 years ago
- Comments: 15 (9 by maintainers)
Our vm is a dual-stack virtual machine, and the yaml of the vm is the same. I am also reproducing what causes paninc. If I make progress, I will sync in time.