Hi; Whats your problematic vm's type is it Debian? Maybe you are affected from the bug CLOUDSTACK-8326? I do not know if this bug has effected on ACS 4.2 release but i know that it effects release 4.8.x 4.9.x
Thanks Özhan On Mon, Nov 7, 2016 at 4:36 PM, Cloud List <cloud-l...@sg.or.id> wrote: > Hi Wei, > > Thanks for your reply. > > I checked and I can confirm that the mac address is listed on > /etc/dhcphosts.txt in VR. > > For example: > > Nov 7 13:30:19 dnsmasq-dhcp[18986]: DHCPDISCOVER(eth0) 06:31:ac:01:13:YY > ignored > Nov 7 13:30:24 dnsmasq-dhcp[18986]: DHCPDISCOVER(eth0) 06:31:ac:01:13:YY > ignored > Nov 7 13:30:33 dnsmasq-dhcp[18986]: DHCPDISCOVER(eth0) 06:31:ac:01:13:YY > ignored > > root@r-4155-VM:/var/log# grep 06:31:ac:01:13:f0 /etc/dhcphosts.txt > 06:31:ac:01:13:YY,X.X.X.X,vm-name,infinite > > YY - last two digits of the mac address > X.X.X.X - ip address which is supposed to be allocated to the VM > > Any advice how can I troubleshoot this further? > > Looking forward to your reply, thank you. > > Cheers. > > > On Mon, Nov 7, 2016 at 9:22 PM, Wei ZHOU <ustcweiz...@gmail.com> wrote: > > > If the mac address is not listed in /etc/dhcphosts.txt in VR, the request > > will be ignored. > > > > Can you give more details so we can reproduce it and fix it ? > > > > -Wei > > > > 2016-11-07 13:44 GMT+01:00 Cloud List <cloud-l...@sg.or.id>: > > > > > 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. > > > > > >
