cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sudha Ponnaganti (JIRA)" <>
Subject [jira] [Created] (CLOUDSTACK-4576) [Portable IP] disassociating a transferred public IP is failing with exception
Date Fri, 30 Aug 2013 21:32:52 GMT
Sudha Ponnaganti created CLOUDSTACK-4576:

             Summary: [Portable IP] disassociating a transferred public IP is failing with
                 Key: CLOUDSTACK-4576
             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: Sudha Ponnaganti
            Priority: Critical
             Fix For: 4.2.0, 4.2.1

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 : 
startIp : 
endip : 
vlan : 33 
subnet : 

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

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


(ii) sequence of things happened as mentioned below 

- disassociate happened without any issues which cleaned the eth interface from router etc..,
 - 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. 

Attaching all the required logs along with db dump to the bug. 

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:

View raw message