cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Srikanteswararao Talluri (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-6853) Fail to remove the network when VM that used to run on this network (but not anymore) still exist
Date Thu, 18 Dec 2014 12:51:13 GMT

     [ https://issues.apache.org/jira/browse/CLOUDSTACK-6853?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Srikanteswararao Talluri closed CLOUDSTACK-6853.
------------------------------------------------

Verified. Closing the bug

> 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.3.4#6332)

Mime
View raw message