Hi Kyle, In my setup I have observed this for stopped VM, the nic table ip4_address set to 'null'. After that I am not able to reproduce the issue. I will keep looking into my setup for this issue.
Can you please send the below commands output from your setup. #select instance_id,ip4_address from nics where instance_id= <instance_id>; #select id, name, private_ip_address from vm_instance where id=<id>; Thanks, Jayapal On 09-Apr-2015, at 6:10 AM, Kyle Flavin <[email protected]> wrote: > 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
