You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@cloudstack.apache.org by "Alena Prokharchyk (JIRA)" <ji...@apache.org> on 2014/05/14 22:45:19 UTC

[jira] [Assigned] (CLOUDSTACK-6676) PublicIpAddress: have to cleanup the resource metadata on ip address release, not on deletion

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

Alena Prokharchyk reassigned CLOUDSTACK-6676:
---------------------------------------------

    Assignee: Nitin Mehta  (was: Alena Prokharchyk)

> PublicIpAddress: have to cleanup the resource metadata on ip address release, not on deletion
> ---------------------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-6676
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6676
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>    Affects Versions: 4.4.0
>            Reporter: Alena Prokharchyk
>            Assignee: Nitin Mehta
>            Priority: Critical
>             Fix For: 4.4.0
>
>
> As public ip address can be assigned to different account over a period of times via associateipAddress/disassociateIpAddress calls, the resource metadata cleanup should happen on disassociate event. Its quite different from other CS objects when the meatadata is cleaned on the object deletion as the ip address doesn't get deleted, but gets released instead.



--
This message was sent by Atlassian JIRA
(v6.2#6252)