[
https://issues.apache.org/jira/browse/CLOUDSTACK-4286?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
venkata swamybabu budumuru closed CLOUDSTACK-4286.
--------------------------------------------------
Have verified it on the latest build. now there is a check to verify startVlan
<= endVlan. if the entered range doesn't satisfy this then it will throw an
error as mentioned below.
"Unable to find guest vlan by range 906-90"
> [DedicatedVLANs] Add few more checks for validating vlanrange parameter with
> "dedicateGuestVlanRange" API
> ---------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-4286
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-4286
> 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 id # e6d03f2322822aee331a1a2aa60190c4c755c402
> Reporter: venkata swamybabu budumuru
> Assignee: Likitha Shetty
> Priority: Minor
> Fix For: 4.2.0
>
> Attachments: logs.tgz
>
>
> Steps to reproduce:
> 1. Have latest CloudStack setup with at least one advance zone.
> 2. Have at least one physical network with following VLANs assigned for guest
> network.
> mysql> select * from physical_network where id=200;
> +-----+--------------------------------------+--------------------+----------------+-----------------+-------+-----------+------------------------+---------+---------------------+---------+
> | id | uuid | name |
> data_center_id | vnet | speed | domain_id | broadcast_domain_range
> | state | created | removed |
> +-----+--------------------------------------+--------------------+----------------+-----------------+-------+-----------+------------------------+---------+---------------------+---------+
> | 200 | a789ff28-577a-4f4e-8623-4a6fa8f716e1 | Physical Network 1 |
> 1 | 901-902,906-908 | NULL | NULL | ZONE | Enabled
> | 2013-08-12 06:22:45 | NULL |
> +-----+--------------------------------------+--------------------+----------------+-----------------+-------+-----------+------------------------+---------+---------------------+---------+
> 3. Make sure one of the above vnets (in my case it is 907) are in use by
> non-ROOT domain account (i.e. domain1Account1)
> 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 | 909 | 204 | 1 | NULL
> | NULL | NULL | NULL |
> | 13 | 910 | 204 | 1 | NULL
> | NULL | NULL | NULL |
> | 14 | 911 | 204 | 1 | NULL
> | NULL | NULL | NULL |
> | 15 | 912 | 204 | 1 |
> fb24d0ea-cfbf-4c9c-a94f-a72f671cfafe | 3 | 2013-08-12 08:39:22 |
> NULL |
> | 16 | 906 | 200 | 1 | NULL
> | NULL | NULL | NULL |
> | 17 | 907 | 200 | 1 |
> 961406af-bfb4-4eb9-ba1e-1e0ee031b24d | 7 | 2013-08-13 09:28:41 |
> NULL |
> | 18 | 908 | 200 | 1 | NULL
> | NULL | NULL | NULL |
> | 19 | 902 | 200 | 1 | NULL
> | NULL | NULL | NULL |
> | 20 | 901 | 200 | 1 | NULL
> | NULL | NULL | NULL |
> +----+------+---------------------+----------------+--------------------------------------+------------+---------------------+---------------------+
> 4. Login as admin and try to dedicated vlan range like "907-90" to a
> different non-ROOT domain account (in my case domain1Account2)
> Observations:
> (i) It went fine. here is the snippet of the API
> _ 1376386828143
> account domain1Account2
> command dedicateGuestVlanRange
> domainid 550918d0-2e1c-47d4-bd1e-05305fa1186e
> physicalnetworkid a789ff28-577a-4f4e-8623-4a6fa8f716e1
> response json
> sessionkey rN+dJLntg/CouOMCEo/oZbrIPg8=
> vlanrange 907-90
> (ii) here is the snippet from db
> mysql> select * from account_vnet_map;
> +----+--------------------------------------+------------+------------+---------------------+
> | id | uuid | vnet_range | account_id |
> physical_network_id |
> +----+--------------------------------------+------------+------------+---------------------+
> | 6 | a8806274-037c-4d2d-a225-d2a83047a071 | 907-90 | 8 |
> 200 |
> +----+--------------------------------------+------------+------------+---------------------+
> 1 row in set (0.00 sec)
> 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
