cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sudha Ponnaganti (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (CLOUDSTACK-4575) [Portable IP] disassociating a transferred public IP is failing with exception
Date Fri, 30 Aug 2013 22:02:51 GMT

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

Sudha Ponnaganti resolved CLOUDSTACK-4575.
------------------------------------------

    Resolution: Fixed
    
> [Portable IP] disassociating a transferred public IP is failing with exception
> ------------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-4575
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4575
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Network Controller
>            Reporter: Chiradeep Vittal
>
> Steps to reproduce: 
> 1. Have latest CloudStack with at least 2 advanced zone. 
> 2. Go to Regions -> local -> portable IP -> add an ip range like below 
> Gateway : 10.147.33.1 
> startIp : 10.147.33.3 
> endip : 10.147.33.10 
> vlan : 33 
> subnet : 255.255.255.128 
> 3. login as a non-ROOT admin 
> username : dom1User1 
> password : password 
> domain : dom1 
> 4. create the following isolated networks in each zone 
> - Network1Zone1 
> - Network1Zone2 
> 5. deploy the following VMs in each network 
> - vm1Zone1 connected to Network1Zone1 
> - vm1Zone2 connected to Network1Zone2 
> 6. Acquire and associate a portable IP to Network1Zone1 
> 7. enable staticNAT on the above portableIP and associate it to vm1Zone2 of Network1Zone2
and add firewall rule for ssh port 
> Observations: 
> (i) portable IP got transferred from Zone1 to Network1Zone2 successfully and able ssh
to the portable IP without any issuees. 
> 8. disassociate above portable IP from Network1Zone2. 
> Observations: 
> (ii) sequence of things happened as mentioned below 
> - disassociate happened without any issues which cleaned the eth interface from router
etc.., but, 
> - it again initiated IPASSOC on its own for the same portable IP which resulted in the
following error and thus this IP stuck in release state forever. 
> (iii) above behaviour made all further IPASSOCs to fail. 

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