Mailing-List: contact issues-help@cloudstack.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@cloudstack.apache.org
Date: Mon, 29 Apr 2013 16:32:15 +0000 (UTC)
From: "Chip Childers (JIRA)" <jira@apache.org>
To: cloudstack-issues@incubator.apache.org
Message-ID: <JIRA.12645253.1367251069470.242643.1367253135987@arcas>
In-Reply-To: <JIRA.12645253.1367251069470@arcas>
References: <JIRA.12645253.1367251069470@arcas>
Subject: [jira] [Resolved] (CLOUDSTACK-2279) Fail to clean up networks if
 expunge initially had a problem
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Chip Childers resolved CLOUDSTACK-2279.
---------------------------------------

    Resolution: Fixed
    
> Fail to clean up networks if expunge initially had a problem
> ------------------------------------------------------------
>
>                 Key: CLOUDSTACK-2279
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2279
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.1.0, 4.2.0
>            Reporter: Marcus Sorensen
>            Assignee: Marcus Sorensen
>            Priority: Critical
>             Fix For: 4.1.0, 4.2.0
>
>
> Noticed today that I had some VMs stuck in expunging state. Looked into it and found that expunge had failed for reasons that are cleared now, but subsequent tries were failing because the IP was already released, and the usage event was getting a null pointer when trying to look up the account.

--
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