You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "ASF subversion and git services (JIRA)" <ji...@apache.org> on 2013/05/27 15:16:20 UTC
[jira] [Commented] (CLOUDSTACK-2700) on network/vpc delete,
portable IP should be still associated with account
[ https://issues.apache.org/jira/browse/CLOUDSTACK-2700?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13667745#comment-13667745 ]
ASF subversion and git services commented on CLOUDSTACK-2700:
-------------------------------------------------------------
Commit 883333c2143e9f3b14a3bc91f8e486e3574dfa37 in branch refs/heads/master from Murali Reddy <mu...@gmail.com>
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=883333c ]
CLOUDSTACK-2700:on network/vpc delete, portable IP should be still
associated with account
Unlike public ip which gets dis-associated (released) with the account
on network/VPC delete, portable IP should continue to be associated with
the account even when the network/VPC with which it is currently
associated in deleted. This fix ensures portable IP are associated to
account even after network/vpc is deleted.
> on network/vpc delete, portable IP should be still associated with account
> --------------------------------------------------------------------------
>
> Key: CLOUDSTACK-2700
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2700
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Network Controller
> Affects Versions: 4.2.0
> Reporter: Murali Reddy
> Assignee: Murali Reddy
> Priority: Critical
> Fix For: 4.2.0
>
>
> Unlike public ip which gets dis-associated (released) with the account on network/VPC delete, portable IP should continue to be associated with the account even when the network/VPC with which it is currently associated in deleted.
--
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