That's right, the correct sequence for DHCP is [1]. But the DHCPREQUEST should be sent by the dhcp client inside the VM. If that is not happening, then I would suggest to check (if any) the logs of the client.
Do you know who can help us with this dhcp client? How is possible to enable the logging?
However I've seen that too using cirros 0.5.2 [2] so maybe we should consider something else. I'll keep checking the logs.
That's right, the correct sequence for DHCP is [1]. But the DHCPREQUEST should be sent by the dhcp client inside the VM. If that is not happening, then I would suggest to check (if any) the logs of the client.
Do you know who can help us with this dhcp client? How is possible to enable the logging?
However I've seen that too using cirros 0.5.2 [2] so maybe we should consider something else. I'll keep checking the logs.
[1]https:/ /paste. opendev. org/show/ bCgFSv49GnS2wBP g2B3I/ /356b2093dea69c 2f8b45- a9b411804046f27 e6dcdc66ce2b9d9 93.ssl. cf1.rackcdn. com/871210/ 8/check/ neutron- ovs-tempest- dvr/2dbee89/ controller/ logs/screen- q-dhcp. txt
[2]https:/