[ https://issues.apache.org/jira/browse/CLOUDSTACK-10081?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16224822#comment-16224822 ]
ASF subversion and git services commented on CLOUDSTACK-10081: -------------------------------------------------------------- Commit ca130488c0c59257724eb4a2f9447f5e384ef6d2 in cloudstack's branch refs/heads/master from [~fmaximus] [ https://gitbox.apache.org/repos/asf?p=cloudstack.git;h=ca13048 ] Merge pull request #2268 from nuagenetworks/bugfix/CLOUDSTACK-10081 CLOUDSTACK-10081: getDevInfo now returns correct value > 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 > > 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)