The DHCP port must be created by the DHCP agent and then bound by OVS (if you are using OVS backend). You should see something like this in the Neutron server:
Provisioning complete for port 4fa9d6bd-ef07-4e9b-badb-fabcd9572088 triggered by entity DHCP.
Provisioning complete for port 4fa9d6bd-ef07-4e9b-badb-fabcd9572088 triggered by entity L2.
This is the message you'll see in the DHCP agent:
DHCP configuration for ports {'4fa9d6bd-ef07-4e9b-badb-fabcd9572088'} is completed
And this in the OVS agent:
Setting status for 4fa9d6bd-ef07-4e9b-badb-fabcd9572088 to UP
Please, try to reproduce the error with the DHCP agent, OVS agent and Neutron server in debug mode, post the logs and the network, subnets and DHCP ports IDs. That will help us to debug this issue.
Hello Shahab:
The DHCP port must be created by the DHCP agent and then bound by OVS (if you are using OVS backend). You should see something like this in the Neutron server: ef07-4e9b- badb-fabcd95720 88 triggered by entity DHCP. ef07-4e9b- badb-fabcd95720 88 triggered by entity L2.
Provisioning complete for port 4fa9d6bd-
Provisioning complete for port 4fa9d6bd-
This is the message you'll see in the DHCP agent: ef07-4e9b- badb-fabcd95720 88'} is completed
DHCP configuration for ports {'4fa9d6bd-
And this in the OVS agent: ef07-4e9b- badb-fabcd95720 88 to UP
Setting status for 4fa9d6bd-
Please, try to reproduce the error with the DHCP agent, OVS agent and Neutron server in debug mode, post the logs and the network, subnets and DHCP ports IDs. That will help us to debug this issue.
Regards.