cloudstack-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sanjeev N (JIRA)" <j...@apache.org>
Subject [jira] [Closed] (CLOUDSTACK-3263) [Multiple_IP_Ranges] IP in revoked state should be freed up after VR restart
Date Mon, 05 Aug 2013 14:04:47 GMT

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

Sanjeev N closed CLOUDSTACK-3263.
---------------------------------


Verified this issue with latest build from ACS 4.2 branch. Now with latest implementation,
alias ip address will be freed up as and when the last vm in the subnet is expunged. Also
if the ip alias is in revoked state, VR restart will remove the entry from nic_ip_alias table
and also deletes that ip address from VR.
                
> [Multiple_IP_Ranges] IP in revoked state should be freed up after VR restart
> ----------------------------------------------------------------------------
>
>                 Key: CLOUDSTACK-3263
>                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3263
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Management Server
>    Affects Versions: 4.2.0
>         Environment: Latest build from master-6-17-stable branch
>            Reporter: Sanjeev N
>            Assignee: Bharat Kumar
>            Priority: Critical
>             Fix For: 4.2.0
>
>         Attachments: management-server.rar
>
>
> IP in revoked state should be freed up after VR restart
> Steps to Reproduce:
> ================
> 1.Bring up CS in basic zone with xen server
> 2.Exhaust all the ip addresses from the guest ip range
> 3.Add another ip range in the new CIDR 
> 4.Deploy guest vm so that IP alias will be created on VR
> 5.Destroy guest vm and wait for it to expunge
> 6.Delete the IP range added at step3 and Simulate network connectivity issue while CS
trying to delete ip alias from router vm (Before deleting the IP range, bring down link local
interface on VR)
> 7.At this state ip alias created at ste4 will be in "revoked" state in nic_ip_alias table.
> 8.Bring up link local interface and reboot VR from CS
> Expected Behavior:
> ===============
> Rebooting VR from CS should perform following:
> 1.Delete ip alias from VR
> 2.Release the ip address and mark the state to "NULL" in user_ip_address table.
> 3.Remove the entry from nic_ip_alis table
> Actual Behavior:
> =============
> Rebooting VR is only deleting the ip alias from VR and not performing the actions 2,3
 mentioned in expected Behavior
> mysql> select * from nic_ip_alias;
> +----+--------------------------------------+--------+---------------+-------------+-----------------+---------------+--------------------+------------+------+-------------+---------------------+------------+-----------+---------+
> | id | uuid                                 | nic_id | ip4_address   | ip6_address |
netmask         | gateway       | start_ip_of_subnet | network_id | vmId | alias_count | created
            | account_id | domain_id | state   |
> +----+--------------------------------------+--------+---------------+-------------+-----------------+---------------+--------------------+------------+------+-------------+---------------------+------------+-----------+---------+
> |  8 | 11d812b4-6cba-4747-b0a2-09c954e4419b |     20 | 10.147.43.132 | NULL        |
255.255.255.192 | 10.147.43.129 | 10.147.43.129      |        204 |   13 |          72 | 2013-06-28
12:08:55 |          2 |         1 | active  |
> |  7 | db940f92-77fe-4d3b-b75e-34e38c3e3933 |     20 | 10.147.43.130 | NULL        |
255.255.255.192 | 10.147.43.129 | 10.147.43.129      |        204 |   13 |          70 | 2013-06-28
11:29:01 |          2 |         1 | revoked |
> +----+--------------------------------------+--------+---------------+-------------+-----------------+---------------+--------------------+------------+------+-------------+---------------------+------------+-----------+---------+
> 2 rows in set (0.00 sec)
> mysql> select * from user_ip_address where id in(125,127);
> +-----+--------------------------------------+------------+-----------+-------------------+----------------+------------+---------------------+------------+----------------+-------+-----------+-------------+-------------------+------------+---------------------+-----------+--------+-----------+-------------+
> | id  | uuid                                 | account_id | domain_id | public_ip_address
| data_center_id | source_nat | allocated           | vlan_db_id | one_to_one_nat | vm_id
| state     | mac_address | source_network_id | network_id | physical_network_id | is_system
| vpc_id | dnat_vmip | is_portable |
> +-----+--------------------------------------+------------+-----------+-------------------+----------------+------------+---------------------+------------+----------------+-------+-----------+-------------+-------------------+------------+---------------------+-----------+--------+-----------+-------------+
> | 125 | 9a331b21-b35a-41a0-883f-9db2ac73a237 |          2 |         1 | 10.147.43.130
    |              1 |          0 | 2013-06-28 11:29:01 |         20 |              0 |  NULL
| Allocated |          70 |               204 |        204 |                 200 |       
 0 |   NULL | NULL      |           0 |
> | 127 | 4e80e813-93fc-4f71-8e94-46d41cffbbbe |          2 |         1 | 10.147.43.132
    |              1 |          0 | 2013-06-28 12:08:55 |         20 |              0 |  NULL
| Allocated |          72 |               204 |        204 |                 200 |       
 0 |   NULL | NULL      |           0 |
> +-----+--------------------------------------+------------+-----------+-------------------+----------------+------------+---------------------+------------+----------------+-------+-----------+-------------+-------------------+------------+---------------------+-----------+--------+-----------+-------------+
> 2 rows in set (0.00 sec)

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