1 Reporting Bugs in Open vSwitch
2 ==============================
4 We are eager to hear from users about problems that they have
5 encountered with Open vSwitch. This file documents how best to report
6 bugs so as to ensure that they can be fixed as quickly as possible.
8 Please report bugs by sending email to bugs@openvswitch.org.
10 The most important parts of your bug report are the following:
12 * What you did that make the problem appear.
14 * What you expected to happen.
16 * What actually happened.
18 Please also include the following information:
20 * The Open vSwitch version number (as output by `ovs-vswitchd
23 * The Git commit number (as output by `git rev-parse HEAD`),
24 if you built from a Git snapshot.
26 * Any local patches or changes you have applied (if any).
28 The following are also handy sometimes:
30 * The kernel version on which Open vSwitch is running (from
31 `/proc/version`) and the distribution and version number of
32 your OS (e.g. "Centos 5.0").
34 * The contents of the vswitchd configuration database (usually
35 `/etc/openvswitch/conf.db`).
37 * The output of `ovs-dpctl show`.
39 * If you have Open vSwitch configured to connect to an
40 OpenFlow controller, the output of `ovs-ofctl show <bridge>`
41 for each `<bridge>` configured in the vswitchd configuration
44 * A fix or workaround, if you have one.
46 * Any other information that you think might be relevant.
48 bugs@openvswitch.org is a public mailing list, to which anyone can
49 subscribe, so please do not include confidential information in your
56 http://openvswitch.org/