If a VMI interface name is not a proper domain name and we use persistent IPs VMIs do not spin

{"controller": "virtualmachineinstance", "controllerGroup": "kubevirt.io", "controllerKind": "VirtualMachineInstance", "VirtualMachineInstance": {"name":"vmi-fedora","namespace":"localnet-subnet-persistent-ips"}, "namespace": "localnet-subnet-persistent-ips", "name": "vmi-fedora", "reconcileID": "d38b83b1-ab26-42c6-8a72-44bf2c638d22", "error": "IPAMClaim.k8s.cni.cncf.io \"vmi-fedora.iface2_myhcp3-hcp3-localnet-ens224\" is invalid: metadata.name: Invalid value: \"vmi-fedora.iface2_myhcp3-hcp3-localnet-ens224\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')"}

This is related to ipamclaims name should follow the RFC 1123 standard

4.18

Always

1. Create a VMI with a interface name with "_" pointing to a ovn-k network with persistent IPs activated

{"controller": "virtualmachineinstance", "controllerGroup": "kubevirt.io", "controllerKind": "VirtualMachineInstance", "VirtualMachineInstance": {"name":"vmi-fedora","namespace":"localnet-subnet-persistent-ips"}, "namespace": "localnet-subnet-persistent-ips", "name": "vmi-fedora", "reconcileID": "d38b83b1-ab26-42c6-8a72-44bf2c638d22", "error": "IPAMClaim.k8s.cni.cncf.io \"vmi-fedora.iface2_myhcp3-hcp3-localnet-ens224\" is invalid: metadata.name: Invalid value: \"vmi-fedora.iface2_myhcp3-hcp3-localnet-ens224\": a lowercase RFC 1123 subdomain must consist of lower case alphanumeric characters, '-' or '.', and must start and end with an alphanumeric character (e.g. 'example.com', regex used for validation is '[a-z0-9]([-a-z0-9]*[a-z0-9])?(\\.[a-z0-9]([-a-z0-9]*[a-z0-9])?)*')"}

VMI is successfully scheduled and ipamclaim created.

We have discover this at hypershift since the additional network generate the interface name and uses underscore for it.