[
https://issues.apache.org/jira/browse/CLOUDSTACK-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16233849#comment-16233849
]
ASF subversion and git services commented on CLOUDSTACK-10081:
--------------------------------------------------------------
Commit 9c7cd8c2485412bc847b2c2473b962fa01435b24 in cloudstack's branch
refs/heads/CLOUDSTACK-10012 from [~sgoeminn]
[ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=9c7cd8c ]
CLOUDSTACK-10081: CloudUtils getDevInfo function will now return "bridge"
instead of "dev" when the name of a ovs bridge is passed.
> 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
> Priority: Major
> 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)
