You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Frank Maximus (JIRA)" <ji...@apache.org> on 2017/10/31 17:21:00 UTC
[jira] [Closed] (CLOUDSTACK-10081) CloudUtils getDevInfo function
only checks for KVM bridgePort and not OVS
[ https://issues.apache.org/jira/browse/CLOUDSTACK-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Frank Maximus closed CLOUDSTACK-10081.
--------------------------------------
> CloudUtils getDevInfo function only checks for KVM bridgePort and not OVS
> -------------------------------------------------------------------------
>
> Key: CLOUDSTACK-10081
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-10081
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the default.)
> Components: cloudstack-agent
> Affects Versions: 4.11.0.0
> Reporter: Sigert Goeminne
> Assignee: Sigert Goeminne
> Fix For: 4.11.0.0
>
>
> CloudUtils getDevInfo function only checks for KVM bridgePort and not OVS. In case you provide an ovsbridge, getDevInfo(dev) will say it's a device instead of a bridge.
> h2. Scenario
> h3. Expected behaviour
> *Given* a KVM Host with openvswitch networking
> *and* kvmnetworklabel of the guest traffic type specifying the name of an existing OVS bridge.
> *When* cloudstack-setup-agent is run on the host
> *Then* the existing openvswitch bridge is used.
> h3. Actual (incorrect) behaviour
> A new bridge cloudbr0 is created in openvswitch.
> and the networking scripts define the new bridge as OVS_BRIDGE in the ifcfg of the existing bridge.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)