I'm trying to get some help understanding the following behavior. Yesterday we had an instance of CloudStack giving out the IP address of a stopped VM to a newly created VM. The existing server was found in the MySQL database with the assigned IP (sanitized outputs):
mysql> select name,private_ip_address,state from vm_instance where name like "<myhost>%"; +--------------------+--------------------+---------+ | name | private_ip_address | state | +--------------------+--------------------+---------+ | <myhost> | 1.1.1.1 | Stopped | +--------------------+--------------------+---------+ The new server booted up, and was given that same 1.1.1.1 IP as well, which caused a conflict in our external host management system. It looks to me like the DHCP lease is expiring on the stopped VM, and then CloudStack is just handing it out again. However, it had previously been explained to me that CloudStack would not hand out IP’s of stopped VM’s (and I do see the IP address registered to the VM in the database). Is that true and is this a possible bug, or is that the expected behavior? -Kyle
