Tomasz Zieba created CLOUDSTACK-4926:
----------------------------------------
Summary: DHCP leases problem after network clean up
Key: CLOUDSTACK-4926
URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4926
Project: CloudStack
Issue Type: Bug
Security Level: Public (Anyone can view this level - this is the default.)
Components: SystemVM
Affects Versions: pre-4.0.0
Environment: CS 3.0.2, XCP 1.1
Reporter: Tomasz Zieba
This would result in the user VM cannot get the IP address after reboot.
After network restart with clean-up option all of the DHCP entries in router's
/etc/dhcphosts.txt and /var/lib/misc/dnsmasq.leases are cleaned up.
Without them it is not possible to get an IP address by the VM. Any attempt to
get one fails with an entry in router's /var/log/dnsmasq.log:
Oct 18 10:29:33 dnsmasq-dhcp[29525]: DHCPDISCOVER(eth0) 02:00:47:5a:00:42 no
address available
The only solution is to stop and then start VM again from Cloudstack UI only.
When VM starts its new DHCP configuration is being sent to the router. DHCP
configuration is not updated even if I restart the network without clean-up
option selected.
We expected that the whole DHCP configuration is generated and sent on network
restart (with or without clean-up option), but it's not. Is this a normal
behavior?
--
This message was sent by Atlassian JIRA
(v6.1#6144)