[jira] [Created] (CLOUDSTACK-5340) [Hyper-V] Control IPs are not getting released when VRs are in stopped state

["Sanjeev N (JIRA)" <ji...@apache.org>]

Sanjeev N created CLOUDSTACK-5340:
-------------------------------------

             Summary: [Hyper-V] Control IPs are not getting released when VRs are in stopped state
                 Key: CLOUDSTACK-5340
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5340
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: Hypervisor Controller, Management Server, Network Controller
    Affects Versions: 4.3.0
         Environment: Latest build from 4.3
            Reporter: Sanjeev N
            Priority: Critical
             Fix For: 4.3.0


[Hyper-V] Control IPs are not getting released when VRs are in stopped state

Steps to Reproduce:
=================
1.Bring up Advanced zone with Hyperv using latest 4.3 build
2.Implement network and make sure Vr is in running state
3.Stop,start VR multiple times.

Expected Result:
==============
Each time VR is stopped, control IP should be released to the pool and when the VR is started again it should get one ip address from the pool.

Actual Result:
===========
When the VR is stopped, control IP is not getting released to the pool. It remains in the reserved state.

Currently in the setup there are only 5 system vms (SSVM,CPVM,3VRs) are there. So in total there should be only 6 controls IPs in reserved state.However op_dc_ip_address_alloc tables shows only one IP in free state out of 10 Pod Ip addresses.

mysql> select * from op_dc_ip_address_alloc;
+----+---------------+----------------+--------+--------+--------------------------------------+---------------------+-------------+
| id | ip_address    | data_center_id | pod_id | nic_id | reservation_id                       | taken               | mac_address |
+----+---------------+----------------+--------+--------+--------------------------------------+---------------------+-------------+
|  1 | 10.147.40.231 |              1 |      1 |      7 | 2709a8d9-71af-4c9b-9139-75e47aad6c76 | 2013-12-02 10:38:36 |           1 |
|  2 | 10.147.40.232 |              1 |      1 |   NULL | NULL                                 | NULL                |           2 |
|  3 | 10.147.40.233 |              1 |      1 |     15 | 2f25a307-9b87-44ae-a6a0-0f97dceada4b | 2013-12-02 10:38:37 |           3 |
|  4 | 10.147.40.234 |              1 |      1 |     23 | 1a1d5501-5e94-46b0-a770-af6277715f74 | 2013-12-02 17:15:05 |           4 |
|  5 | 10.147.40.235 |              1 |      1 |     18 | 02e7a340-d1f3-46ab-adb9-dd91c3549d30 | 2013-12-02 15:44:13 |           5 |
|  6 | 10.147.40.236 |              1 |      1 |     28 | 762014f4-fcd8-41d9-906c-1b05dbf07df7 | 2013-12-02 17:54:00 |           6 |
|  7 | 10.147.40.237 |              1 |      1 |     18 | ced340b8-a34e-43fe-829e-7b790e380387 | 2013-12-02 15:25:37 |           7 |
|  8 | 10.147.40.238 |              1 |      1 |     14 | 2f25a307-9b87-44ae-a6a0-0f97dceada4b | 2013-12-02 10:38:36 |           8 |
|  9 | 10.147.40.239 |              1 |      1 |     23 | c2e2d7b1-4b4f-48da-b9ba-a8e64255711b | 2013-12-02 17:36:45 |           9 |
| 10 | 10.147.40.240 |              1 |      1 |     18 | cb036c69-1721-4d13-b61d-42b6f2e7a76c | 2013-12-02 17:50:20 |          10 |
+----+---------------+----------------+--------+--------+--------------------------------------+---------------------+-------------+
10 rows in set (0.00 sec)
mysql> select id,name,state from vm_instance where removed is null and vm_type!='User';
+----+---------+----------+
| id | name    | state    |
+----+---------+----------+
|  2 | v-2-VM  | Running  |
|  4 | s-4-VM  | Running  |
|  6 | r-6-VM  | Stopped  |
|  9 | r-9-VM  | Stopped  |
| 11 | r-11-VM | Starting |
+----+---------+----------+
5 rows in set (0.00 sec)

Attaching management server log file with this.



--
This message was sent by Atlassian JIRA
(v6.1#6144)