cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "ASF subversion and git services (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (CLOUDSTACK-3463) [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP
Date Mon, 15 Jul 2013 04:24:50 GMT

    [ https://issues.apache.org/jira/browse/CLOUDSTACK-3463?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13708229#comment-13708229
] 

ASF subversion and git services commented on CLOUDSTACK-3463:
-------------------------------------------------------------

Commit 0c32466a758ed7be643488d5cc7ec6d6e267da30 in branch refs/heads/master from [~murali.reddy]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=0c32466 ]

CLOUDSTACK-3463: [Portable IP] [EIP/ELB Zone] EIP semantics are not
intact with portable IP

fix ensures that, on release of portable IP associated with 'EIP
enabled' basic zone vm, a new system public IP is allocated and
associated with the VM

                
> [Portable IP] [EIP/ELB Zone] EIP semantics are not intact with portable IP 
> ---------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3463
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3463
>             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
>         Environment: commit id # 67cab313c969e5f488d6c0f92f9ec058288a96a0
>            Reporter: venkata swamybabu budumuru
>            Assignee: Murali Reddy
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have latest CloudStack setup with EIP / ELB enabled zone using the default EIP/ELB
network offering.
> 2. Deploy a VM.
> 3. By default VM is associated with is_system=1 public ip address
> 4. Acquire a portable IP and enable static NAT on the portable IP
> Observations:
> (i) the default is_system=1 public ip address was released and static nat enabled on
the new portable IP and everything is fine as expected.
> 5. Disassociate the portable IP that was acquired in step : 4
> Observations:
> (ii) Portable IP got released without any issue but, didn't see any is_system=1 public
IP associated with user VM.
> 2013-07-11 10:21:55,044 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-43:job-216)
Schedule queued job-216
> 2013-07-11 10:21:55,075 DEBUG [cloud.async.SyncQueueManagerImpl] (Job-Executor-43:job-216)
There is a pending process in sync queue(id: 80)
> 2013-07-11 10:21:55,076 DEBUG [cloud.async.AsyncJobManagerImpl] (Job-Executor-44:job-216)
Executing org.apache.cloudstack.api.command.user.address.DisassociateIPAddrCmd for job-216
> 2013-07-11 10:21:55,102 DEBUG [cloud.user.AccountManagerImpl] (Job-Executor-44:job-216)
Access to Ip[10.147.45.223-3] granted to Acct[9-dom1Acc5] by DomainChecker_EnhancerByCloudStack_9ffe9015
> 2013-07-11 10:21:55,104 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-44:job-216)
Revoking all Firewallrules as a part of public IP id=217 release...
> 2013-07-11 10:21:55,106 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-44:job-216)
Releasing 0 firewall rules for ip id=217
> 2013-07-11 10:21:55,108 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-44:job-216)
There are no firewall rules to apply
> 2013-07-11 10:21:55,110 DEBUG [network.firewall.FirewallManagerImpl] (Job-Executor-44:job-216)
Successfully released firewall rules for ip id=217 and # of rules now = 0
> 2013-07-11 10:21:55,110 DEBUG [cloud.network.NetworkManagerImpl] (Job-Executor-44:job-216)
Revoking all PortForwarding/StaticNat rules as a part of public IP id=217 release...
> (iii) at this moment user VM is neither associated with any EIP nor with any portable
IP.
> Attaching all the required logs along with db dump.

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

Mime
View raw message