Hi, After our upgrade from CloudStack 4.2 to 4.8.1.1, we noted that some (but not all) of our VMs are not able to get DHCP from the VR. This gives problem when the VM is restarted and cannot get up and running because unable to get IP.
I logged in to the VR and found below messages showing that the DHCP server is ignoring the request from the VM. Nov 7 12:19:43 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Nov 7 12:19:52 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:05:64:01:13:d3 ignored Nov 7 12:19:53 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Nov 7 12:20:04 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Nov 7 12:20:11 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:05:64:01:13:d3 ignored Nov 7 12:20:22 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Nov 7 12:20:30 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Nov 7 12:20:42 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Nov 7 12:21:02 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Nov 7 12:21:19 dnsmasq-dhcp[29938]: DHCPDISCOVER(eth0) 06:44:da:01:13:98 ignored Any reason why the dnsmasq service ignored the request from the VM and how can we fix that? At the moment, the only workaround we can do is to configure the IP address statically to the servelet, which is not practical. Any advice is greatly appreciated. Thank you.
