cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Marcus Sorensen (JIRA)" <>
Subject [jira] [Commented] (CLOUDSTACK-1096) guest traffic types on multiple networks don't work,this bug is not fixed in 4.0.1
Date Fri, 01 Feb 2013 04:01:14 GMT


Marcus Sorensen commented on CLOUDSTACK-1096:

Here is the original line from the commit you specify. Notice it has an escape after the 's',
and it works identically to your second line.

String cmdout = Script.runSimpleBashScript("brctl show | tail -n +2 | grep -v \"^\\s\"|awk
'{print $1}'|sed '{:q;N;s/\\n/%/g;t q}'");

What problem did you come across that you're blaming on this?
> guest traffic types on multiple networks don't work,this bug is not fixed in 4.0.1
> ----------------------------------------------------------------------------------
>                 Key: CLOUDSTACK-1096
>                 URL:
>             Project: CloudStack
>          Issue Type: Bug
>      Security Level: Public(Anyone can view this level - this is the default.) 
>          Components: Hypervisor Controller, Install and Setup, KVM
>    Affects Versions: 4.0.1
>         Environment: ubuntu 12.04 server
>            Reporter: terryye
>              Labels: guest, kvm, lable, vlan
>   Original Estimate: 72h
>  Remaining Estimate: 72h
> This bug is not fixed . 
> commit 915babd970a9b4f209deceb3c4973b7d1c9c0c12
> Author: Marcus Sorensen <>
> Date:   Wed Sep 26 17:14:57 2012 -0700
>     fix kvm traffic labels (guest traffic types on multiple networks don't
>     work)
>     Cloudstack seems to let you create guest traffic types on multiple
>     physical networks. However, when I try this with KVM I end up always
>     bridging to whatever device is used for This pulls
>     the traffic label (NicTO.getName()) and uses that bridge to ensure that
>     we get on the correct physical network, rather than just always using
>     the
>     This also changes the bridge naming scheme from cloudVirBr + vlanid to
>     br + physicalinterface + "-" + vlanid. This is because we should be able
>     to support the same vlan numbers per physical network, and the previous
>     bridge name would not support this and collide.

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:

View raw message