Red Hat Bugzilla – Bug 1242497
RFE: add support to highlight DB/DP inconsistencies
Last modified: 2016-04-26 18:39:08 EDT
Description of problem: OVS tracks its ports in a database in userspace, but those interfaces may not be part of the datapath causing troubles and confusion. Since plotnetcfg builds a diagram the network on complex environment including OVS, it would be great if it could highlight such cases so that one could spot the problem easily.
Support for this is already in the plotnetcfg git, will be part of the next version.
Fixed in plotnetcfg 0.4.1, available in Fedora and EPEL7. Not sure how this works with RHOS.
Hi Lon, Could you explain the steps to update the package on RHOS? Thanks, fbl
Hi Jiri, We'd like to understand this RFE from testing point of view in order to prioritize it properly. What kind of action required from QE, in order to test it?
ip l a type veth ovs-vsctl add-br ovs0 ovs-vsctl add-port ovs0 veth0 ip l d veth0 ip l a type veth plotnetcfg | dot -Tpdf The real "veth0" interface (the one in the red/green/gray box) should not be shown as connected to the "ovs0" interface. Instead, it should be unconnected and there should be a separate "veth0" interface in a dotted box connected to the "ovs0" bridge. Please note that future ovs versions (>=2.5) will reconnect the interfaces automatically, thus make this harder to reproduce.
Jiri, thanks for the explanation, we would like to test plotencfg, as it seems to be also very helpful as a debugging tool in complex ovs environment.
from quick read through it looks like later version of plotnetcfg addresses this RFE updating to Modified but would like input if there is more than a simple package update for OSP 8.
Have tested on latest osp8 AIO from /OpenStack/8.0-RHEL-7/2016-02-11.2 VLANs and VXLAN environments - see attached files. The scenario you've written in comment #10 passed successfully as well.
Created attachment 1127038 [details] VLAN and VXLAN
Created attachment 1127039 [details] AIO with reproduced steps
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHEA-2016-0603.html