[Neutron] DHCP port status inactive
Hello, I am new to Openstack environment and I need help with a Neutron problem. When I create a new network, the DHCP port launches with status inactive. Even though I tried to create a VM, the DHCP generate a port for the machine, However it takes a few minutes to give an error: "Build of instance ed6c8835-f2d4-4730-9638-74ded388361b aborted: Failed to allocate the network(s), not rescheduling." The only alternative solution to overcome this issue is to change the DHCP agent of the network. If I change it, the new DHCP port will have an active status and then I can launch a VM. Nothing conclusive was found in the logs, just the error to bind the port. It doesn't say anything to why the port is inactive, just that the port was created and with status active. Things that I already tried: -> See nova and neutron logs -> Restart neutron-server, neutron-dhcp-agent, neutron-openvswitch-agent -> Change manually the DHCP agent Anyone had the same problem as this one? Any tips to troubleshoot? Any help is welcome! Thanks.
Hi, Dnia poniedziałek, 16 grudnia 2024 16:18:49 czas środkowoeuropejski standardowy Vinicius Afonso pisze:
Hello,
I am new to Openstack environment and I need help with a Neutron problem.
When I create a new network, the DHCP port launches with status inactive. Even though I tried to create a VM, the DHCP generate a port for the machine, However it takes a few minutes to give an error:
"Build of instance ed6c8835-f2d4-4730-9638-74ded388361b aborted: Failed to allocate the network(s), not rescheduling."
The only alternative solution to overcome this issue is to change the DHCP agent of the network. If I change it, the new DHCP port will have an active status and then I can launch a VM.
Nothing conclusive was found in the logs, just the error to bind the port. It doesn't say anything to why the port is inactive, just that the port was created and with status active.
The fact that port is not bound is the reason why it is not active. Port needs to be bound first to be able to switch to active state. So you need to check the reason why port failed to be bound to the host where this DHCP agent lives.
Things that I already tried:
-> See nova and neutron logs -> Restart neutron-server, neutron-dhcp-agent, neutron-openvswitch-agent -> Change manually the DHCP agent
Anyone had the same problem as this one? Any tips to troubleshoot?
Any help is welcome!
Thanks.
-- Slawek Kaplonski Principal Software Engineer Red Hat
participants (2)
-
Sławek Kapłoński
-
Vinicius Afonso