You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Geoff Higgibottom (JIRA)" <ji...@apache.org> on 2014/02/18 00:40:19 UTC
[jira] [Commented] (CLOUDSTACK-6131) [Automation] unable to
dedicate a vlan range
[ https://issues.apache.org/jira/browse/CLOUDSTACK-6131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13903600#comment-13903600 ]
Geoff Higgibottom commented on CLOUDSTACK-6131:
-----------------------------------------------
I have tried to reproduce this manually and have not been able to re-create the issue. Added a new Guest VLAN Range in addition to the existing range, then dedicated to a normal user account, all successful, and all on the latest RC (fifth round).
> [Automation] unable to dedicate a vlan range
> ---------------------------------------------
>
> Key: CLOUDSTACK-6131
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-6131
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: Management Server
> Affects Versions: 4.3.0
> Reporter: Srikanteswararao Talluri
> Priority: Blocker
> Fix For: 4.3.0
>
>
> Steps to reproduce:
> ===================
> #1. List the available physical network using ListPhysicalNetwork
> # 2. Add a Guest Vlan range to the available physical network using UpdatePhysicalNetwork
> # 3. Dedicate the created guest vlan range to user account using DedicateGuestVlanRange
> Link to automated test failure:
> http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-smoke-matrix-4.3/1194/suite=test_guest_vlan_range/testReport/integration.smoke.test_guest_vlan_range/TestDedicateGuestVlanRange/test_dedicateGuestVlanRange/
> Link to management server log:
> http://jenkins.buildacloud.org/view/cloudstack-qa-4.3/job/test-matrix-4.3/distro=centos63,hypervisor=kvm,profile=kvm-centos63/lastSuccessfulBuild/artifact/246.tar.bz2
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)