[
https://issues.apache.org/jira/browse/CLOUDSTACK-6832?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14116814#comment-14116814
]
Murali Reddy commented on CLOUDSTACK-6832:
------------------------------------------
Problem;
-----------
Ovs network guru allocates a vnet from the configured pool of vnet ranges, when
it designs network. It is supposed to release the allocated vnet when network
is destroyed. As reported by the bug, vnet is not released.
Root Cause Analysis:
--------------------------
Root cause is missing code to release the vnet when network is deleted.
Proposed Solution:
------------------------
release the allocated vnet for the network when network is deleted.
QA steps:
-------------
QA need to verify that once network is destroyed vnet is released.
there is no test case to test if vnet is indeed released when network id
destroyed.
> [OVS]vnet is not released even the network is deleted
> -----------------------------------------------------
>
> Key: CLOUDSTACK-6832
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6832
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server, Network Controller
> Affects Versions: 4.4.0
> Environment: Latest build from 4.4 with commit
> 32bbc84db99d0e5f7f9b2a3fb41e4e783a2de350
> Reporter: Sanjeev N
> Assignee: Murali Reddy
> Priority: Critical
> Labels: ovs
> Fix For: 4.4.0
>
> Attachments: management-server.rar
>
>
> [OVS]vnet is not released even the network is deleted
> Steps to reproduce:
> ===============
> 1.Bring up CS in advanced zone with xen cluster
> 2.Create physical network with GRE isolation and specify some VNIs as GRE
> keys for guest traffic
> 3.Create network offering with virtual networking and OVS as the service
> provider
> 4.Deploy few vms with the above network
> 5.Delete the network after expunging all the vms
> Result:
> =====
> Network deletion was successful but the vnet allocated for the network was
> not released.
> VNI range specified for the guest traffic was 981-1000 and 992 was taken for
> the implemented network. But the vnet id 992 was not released back to the
> pool even after deleting the network.
> mysql> select * from op_dc_vnet_alloc;
> +-----+------+---------------------+----------------+--------------------------------------+------------+---------------------+---------------------+
> | id | vnet | physical_network_id | data_center_id | reservation_id
> | account_id | taken | account_vnet_map_id |
> +-----+------+---------------------+----------------+--------------------------------------+------------+---------------------+---------------------+
> | 122 | 989 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 123 | 988 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 124 | 987 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 125 | 982 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 126 | 981 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 127 | 986 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 128 | 985 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 129 | 984 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 130 | 983 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 131 | 996 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 132 | 997 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 133 | 994 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 134 | 995 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 135 | 992 | 203 | 2 |
> 8edad56a-a59d-4477-8741-9e91a8ef9052 | 2 | 2014-06-03 15:12:55 |
> NULL |
> | 136 | 993 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 137 | 990 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 138 | 991 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 139 | 1000 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 140 | 998 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> | 141 | 999 | 203 | 2 | NULL
> | NULL | NULL | NULL |
> +-----+------+---------------------+----------------+--------------------------------------+------------+---------------------+---------------------+
> 20 rows in set (0.00 sec)
> Please look for job-212 in the attached MS log file.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
