DPDK: VM getting IP from invalid dhcp response with src ip and option-router as 0.0.0.0

[Vinod Nair]

Sometimes on Spawning a vm , it is getting ip from DHCPserver with nexthop as 0.0.0.0

0:05:38.227226 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 02:ae:9b:aa:9e:df (oui Unknown), length 300
20:05:38.227253 IP 0.0.0.0.bootps > 140.3.0.3.bootpc: BOOTP/DHCP, Reply, length 274
20:05:38.227253 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 02:ae:9b:aa:9e:df (oui Unknown), length 300
20:05:38.227254 IP 0.0.0.0.bootps > 140.3.0.3.bootpc: BOOTP/DHCP, Reply, length 274
20:05:38.923238 IP6 fe80::ae:9bff:feaa:9edf > ip6-allrouters: ICMP6, router solicitation, length 16
20:05:42.587239 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 02:ae:9b:aa:9e:df (oui Unknown), length 300
20:05:42.587242 IP 0.0.0.0.bootps > 140.3.0.3.bootpc: BOOTP/DHCP, Reply, length 274
20:05:42.587243 IP 0.0.0.0.bootpc > 255.255.255.255.bootps: BOOTP/DHCP, Request from 02:ae:9b:aa:9e:df (oui Unknown), length 300
20:05:42.587243 IP 0.0.0.0.bootps > 140.3.0.3.bootpc: BOOTP/DHCP, Reply, length 274

Version: 3.0-2704~kilo

[Hari Prasad Killi (haripk)]

Please check if Agent had the VM interface in active state or not. If the config is not completely downloaded, this is the behavior, with the VM getting a short lease (valid for 4 seconds only). Upon expiry, VM requests again and when config is downloaded, it would get the final lease. If it continues to be like this, there could be a problem with the config download to agent.

[Raja Sivaramakrishnan (raja-u)]

Vinod, can you please close if this is not seen any more (please see Haris comment in audit trail)?

[Vinod Nair (vinodnair)]

This issue is not seen in latest images