[
https://issues.apache.org/jira/browse/CLOUDSTACK-4105?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13730660#comment-13730660
]
Bharat Kumar commented on CLOUDSTACK-4105:
------------------------------------------
in case when we are trying to remove all the vlans, we do not throw a error
message if some vnets are allocated. Also in this case vnet column in physical
networks table is not updated properly.
> Vnet's from Phisical network's table are getting deleted even the Vnet is
> used by Phisical network.
> ---------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4105
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4105
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Install and Setup
> Affects Versions: 4.2.0
> Reporter: Kiran Koneti
> Assignee: Bharat Kumar
> Priority: Critical
> Fix For: 4.2.0
>
>
> Steps are as follows:
> 1)Created a Advance zone setup using the Vnet range 1100-1109.
> 2)Once the setup is up created a VM which intern created a Physical network
> with the Vnet 1106.
> 3)Then Suing the API update Physical network I tried to remove the Vlan range
> 1100-1109.
> 4)The Vlan range from the physical network table is removed without any error
> message.
> 5)but the op_dc_vnet_alloc table still has the entry for the Vlan associated
> with the Phisical network.
> The below two tables show the db entries:
> The Physical network table in the before deleting
> mysql> select * from physical_network;
> +-----+--------------------------------------+--------------------+----------------+-----------+-------+-----------+------------------------+---------+---------------------+---------+
> | id | uuid | name |
> data_center_id | vnet | speed | domain_id | broadcast_domain_range |
> state | created | removed |
> +-----+--------------------------------------+--------------------+----------------+-----------+-------+-----------+------------------------+---------+---------------------+---------+
> | 200 | 85b82257-fc88-4eec-bf31-8995a6d27535 | Physical Network 1 |
> 1 | 1100-1109 | NULL | NULL | ZONE | Enabled |
> 2013-08-06 14:38:00 | NULL |
> +-----+--------------------------------------+--------------------+----------------+-----------+-------+-----------+------------------------+---------+---------------------+---------+
> 1 row in set (0.00 sec)
> The Phisical network tabble after the deletion
> mysql> select * from physical_network;
> +-----+--------------------------------------+--------------------+----------------+------+-------+-----------+------------------------+---------+---------------------+---------+
> | id | uuid | name |
> data_center_id | vnet | speed | domain_id | broadcast_domain_range | state
> | created | removed |
> +-----+--------------------------------------+--------------------+----------------+------+-------+-----------+------------------------+---------+---------------------+---------+
> | 200 | 85b82257-fc88-4eec-bf31-8995a6d27535 | Physical Network 1 |
> 1 | NULL | NULL | NULL | ZONE | Enabled |
> 2013-08-06 14:38:00 | NULL |
> +-----+--------------------------------------+--------------------+----------------+------+-------+-----------+------------------------+---------+---------------------+---------+
> 1 row in set (0.00 sec)
> The op_dc_vnet_alloc table after deletion
> mysql> select * from op_dc_vnet_alloc;
> +----+------+---------------------+----------------+----------------+------------+-------+---------------------+
> | id | vnet | physical_network_id | data_center_id | reservation_id |
> account_id | taken | account_vnet_map_id |
> +----+------+---------------------+----------------+----------------+------------+-------+---------------------+
> | 12 | 1106 | 200 | 1 | NULL |
> NULL | NULL | NULL |
> +----+------+---------------------+----------------+----------------+------------+-------+---------------------+
>
--
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
