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-2609) [MultipleIPsPerNic][SharedNetworks] nic_secondary_ips account/domainid is different when compared with primary ups
Date Tue, 21 May 2013 15:13:16 GMT
venkata swamybabu budumuru created CLOUDSTACK-2609:
------------------------------------------------------

             Summary: [MultipleIPsPerNic][SharedNetworks] nic_secondary_ips account/domainid
is different when compared with primary ups
                 Key: CLOUDSTACK-2609
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2609
             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 # 85d54cd1c088997dd08f0328984bee1a55703636
            Reporter: venkata swamybabu budumuru
            Assignee: Jayapal Reddy
             Fix For: 4.2.0


Steps to reproduce :

1. Have latest CloudStack with advanced zone having KVM cluster with 1 host
2. Have at least one non-ROOT domain user
3. Create at least one share network with scope set domain of the above user
4. deploy a VM connected to the above shared networks
5. acquire at least one secondary ips for the above NICs

Observations :

(i) verify in the db cloud.nic_secondary_ips for account and domain id info.

here is the snapshot of the db


mysql> select * from nic_secondary_ips;
+----+--------------------------------------+------+-------+---------------+-------------+------------+---------------------+------------+-----------+
| id | uuid                                 | vmId | nicId | ip4_address   | ip6_address |
network_id | created             | account_id | domain_id |
+----+--------------------------------------+------+-------+---------------+-------------+------------+---------------------+------------+-----------+
|  4 | 8402dfa2-94b2-4001-8c2c-b52d5c76bbad |   27 |    69 | 10.147.44.235 | NULL        |
       217 | 2013-05-21 19:49:40 |          1 |         1 |
|  5 | 43954e3e-c5bf-4833-983c-9aec27a27e14 |   27 |    70 | 10.147.54.235 | NULL        |
       218 | 2013-05-21 19:54:24 |          1 |         1 |
+----+--------------------------------------+------+-------+---------------+-------------+------------+---------------------+------------+-----------+

(ii) Here is the snapshot of user_ip_address that contains the primary ip address info


mysql> select * from user_ip_address where id=42\G
*************************** 1. row ***************************
                 id: 42
               uuid: a744755a-f5cd-4959-b338-1c36eaa56c32
         account_id: 4
          domain_id: 2
  public_ip_address: 10.147.54.231
     data_center_id: 3
         source_nat: 0
          allocated: 2013-05-21 17:49:41
         vlan_db_id: 5
     one_to_one_nat: 0
              vm_id: NULL
              state: Allocated
        mac_address: 32
  source_network_id: 218
         network_id: NULL
physical_network_id: 202
          is_system: 0
             vpc_id: NULL
          dnat_vmip: NULL
1 row in set (0.00 sec)

(iii) In case of user_ip_address, it contains the account and domain id of the user who deployed
the vm but, in case of secondary IPs, it contains the account and domain id as 1.

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: http://www.atlassian.com/software/jira

Mime
View raw message