cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "venkata swamybabu budumuru (JIRA)" <j...@apache.org>
Subject [jira] [Created] (CLOUDSTACK-3394) [portable IP] unable to transfer IP across zones
Date Mon, 08 Jul 2013 10:01:48 GMT
venkata swamybabu budumuru created CLOUDSTACK-3394:
------------------------------------------------------

             Summary: [portable IP] unable to transfer IP across zones
                 Key: CLOUDSTACK-3394
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3394
             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 # 10d9e5965a687c0c2d1d6c3e57f38602420720d6
            Reporter: venkata swamybabu budumuru
            Assignee: Murali Reddy
             Fix For: 4.2.0


Steps to reproduce:

1. Have latest CloudStack setup 
2. create at least 2 advanced zones (zone1, zone2)
3. add a portable ip range : 10.147.49.220-239/24
4. Have at least one non-ROOT domain user.
5. Login as the above user and create at least 1 network in each zone (Network1, Network2)
6. acquire IP (with cross zones : YES) and associate IP to Network1
7. enable staticNat on the IP acquired in Step: 6 with a VM created in zone2

Observations: 

(i) It failed with the following error in the mgmt server logs

2013-07-08 10:53:34,893 INFO  [cloud.api.ApiServer] (catalina-exec-8:null) Unable to create
ip forwarding rule, IP address Ip[10.147.49.221-1] is not in the same availability zone as
virtual machine VM[User|Zone2VM1]
2013-07-08 10:53:34,896 DEBUG [cloud.api.ApiServlet] (catalina-exec-8:null) ===END===  10.252.192.25
-- GET  apiKey=MdUSVCKSP3sL6ptU2mvdqdF4QcRe5vl2gosM74JOZmIVEjzCpVKtABltph2gEC1u1TBadFcjvRaiHGVEhFddNg&command=enableStaticNat&ipaddressid=42fa6947-6987-4d88-9d4d-f9c50ea9fe27&networkid=2c0e7246-c41a-490b-9852-ee886381659c&response=json&virtualmachineid=a3625eef-6f56-4d71-9d1d-67e9c7418206&signature=RDNschQ2tihuCpAItfc1ltzzPcs%3D

(ii) At the end I could see that the public ip has been transferred from one network to the
other but the datacenter id is not updated. 

(iii) Here is the snippet from cloud.user_ip_address table.

*************************** 22. row ***************************
                 id: 22
               uuid: 42fa6947-6987-4d88-9d4d-f9c50ea9fe27
         account_id: 3
          domain_id: 2
  public_ip_address: 10.147.49.221
     data_center_id: 1
         source_nat: 0
          allocated: 2013-07-08 14:52:49
         vlan_db_id: 4
     one_to_one_nat: 0
              vm_id: NULL
              state: Allocated
        mac_address: 0
  source_network_id: 200
         network_id: 209
physical_network_id: 200
          is_system: 0
             vpc_id: NULL
          dnat_vmip: NULL
        is_portable: 1
22 rows in set (0.00 sec)

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