VM Build Fails as Network Fails to Get due to Allocated
Problem
The VM build is failing due to the network not being allocated, although the network agents remain running and in a healthy state.
x
//Server show{u'message': u'Build of instance 79ced397-30e7-4f00-bf3b-16ba3060f695 aborted: Failed to allocate the network(s), not rescheduling.', u'code': 500,..raise exception.VirtualInterfaceCreateException()\nnova.exception.VirtualInterfaceCreateException: Virtual Interface creation failed\n\nDuring handling of the above exception, another exception occurred}//Messages logsSep 10 01:09:37 p2l00310 NetworkManager[3439]: <warn> [1725930577.9950] dhcp4 (ens3f0): request timed outSep 10 01:09:37 p2l00310 NetworkManager[3439]: <info> [1725930577.9958] dhcp4 (ens3f0): state changed unknown -> timeoutSep 10 01:09:38 p2l00310 NetworkManager[3439]: <info> [1725930578.0150] dhcp4 (ens3f0): canceled DHCP transaction, DHCP client pid 58704Sep 10 01:09:38 p2l00310 NetworkManager[3439]: <info> [1725930578.0151] dhcp4 (ens3f0): state changed timeout -> doneSep 10 01:09:38 p2l00310 NetworkManager[3439]: <info> [1725930578.0154] device (ens3f0): state change: ip-config -> failed (reason 'ip-config-unavailable', sys-iface-state: 'managed')..Sep 10 01:09:38 p2l00310 ovs-vswitchd: ovs|7389400|netlink_socket|ERR|transaction error (Invalid argument)Sep 10 01:09:38 p2l00310 kernel: selinux_nlmsg_perm: 18 callbacks suppressed//The "openvswitch.service" active but lists errors like:Sep 10 10:55:08 p2l00310.dc02.its.hpecorp.net ovs-vswitchd[3347]: ovs|7400080|netlink_socket|ERR|transaction error (Invalid argument)Sep 10 10:55:08 p2l00310.dc02.its.hpecorp.net ovs-vswitchd[3347]: ovs|7400081|netlink_socket|ERR|transaction error (Invalid argument)Sep 10 10:55:09 p2l00310.dc02.its.hpecorp.net ovs-vswitchd[3347]: ovs|7400083|netlink_socket|ERR|transaction error (Invalid argument)Environment
- Platform9 Managed OpenStack - v4.0 and Higher
Cause
VM virtual network Interface creation fails as OVS and host encounters network transaction errors.
Resolution
The services given below need to be restarted to fix the issue. Ensure all services are up and running. Once services are stable, attempt to build the new instance.
$ systemctl restart openvswitch$ systemctl restart pf9-neutron-ovs-agent$ systemctl restart systemd-machinedAdditional Information
The underlying Linux host may experience network issues, but restarting the services typically resolves the problem.
Was this page helpful?