[
https://issues.apache.org/jira/browse/CLOUDSTACK-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alena Prokharchyk resolved CLOUDSTACK-6853.
-------------------------------------------
Resolution: Fixed
Fixed with 11d8c953e3bc3fdb495aa51245f3736e60128bc2
> Fail to remove the network when VM that used to run on this network (but not
> anymore) still exist
> -------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-6853
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6853
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.4.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Priority: Critical
> Fix For: 4.4.0
>
>
> Steps to reproduce:
> 1) Create 2 networks
> 2) Deploy vm in network1.
> 3) Add vm to network2 using addNic api.
> 4) Remove vm from network2 using removeNic api.
> Try to remove the network2. The removal should be successful as there are no
> vms belong to it anymore.
> Bug: the network fails to remove, and the error message says that there is a
> vm (created on step2) still belonging to the network.
> Its a bug in the DB search method where we look for the VM in a particular
> network. In this case we do joins between table1=user_vm and table2=nics
> based on instance_id. As long as the result in table1 (vm) is not removed,
> its being returned to the user when the matching record is found in table2,
> no matter if the record in table2 is removed or not. It just has to exist
> there.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
