[
https://issues.apache.org/jira/browse/CLOUDSTACK-3957?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Marcus Sorensen closed CLOUDSTACK-3957.
---------------------------------------
Resolution: Fixed
I believe there may still be a core issue here, but since we can't reliably
reproduce, this fix verifies that after we have checked that no VMs are running
on the network, we update op_networks accordingly and continue on with the
network removal process.
this should go into 4.1.2, if there is one. There was none in the dropdown.
> op_networks table isn't always accurate, leading to failure in
> account/network cleanup
> --------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3957
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3957
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.1.1, 4.2.0
> Reporter: Marcus Sorensen
> Assignee: Marcus Sorensen
> Fix For: 4.2.0
>
>
> Occasionally we see issues in account deletion, where a network fails to
> clean up. The error might be:
> 2013-07-30 10:08:01,995 DEBUG [cloud.network.NetworkManagerImpl]
> (AccountChecker-1:null) Unable to remove the network id=766 as it has active
> Nics.
> But inspecting the cloud.nics table, all nics are removed. I've not yet
> figured out how to reproduce it, but in our test environment, dozens of
> accounts are created/deleted per day against a long-lived zone, and these
> tend to build up.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
