REPORTING-BUGS.md

   1 Reporting Bugs in Open vSwitch
   2 ==============================
   3
   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.
   7
   8 Please report bugs by sending email to bugs@openvswitch.org.
   9
  10 For reporting security vulnerabilities, please read SECURITY.md.
  11
  12 The most important parts of your bug report are the following:
  13
  14   * What you did that make the problem appear.
  15
  16   * What you expected to happen.
  17
  18   * What actually happened.
  19
  20 Please also include the following information:
  21
  22   * The Open vSwitch version number (as output by `ovs-vswitchd
  23     --version`).
  24
  25   * The Git commit number (as output by `git rev-parse HEAD`),
  26     if you built from a Git snapshot.
  27
  28   * Any local patches or changes you have applied (if any).
  29
  30 The following are also handy sometimes:
  31
  32   * The kernel version on which Open vSwitch is running (from
  33     `/proc/version`) and the distribution and version number of
  34     your OS (e.g. "Centos 5.0").
  35
  36   * The contents of the vswitchd configuration database (usually
  37     `/etc/openvswitch/conf.db`).
  38
  39   * The output of `ovs-dpctl show`.
  40
  41   * If you have Open vSwitch configured to connect to an
  42     OpenFlow controller, the output of `ovs-ofctl show <bridge>`
  43     for each `<bridge>` configured in the vswitchd configuration
  44     database.
  45
  46   * A fix or workaround, if you have one.
  47
  48   * Any other information that you think might be relevant.
  49
  50 bugs@openvswitch.org is a public mailing list, to which anyone can
  51 subscribe, so please do not include confidential information in your
  52 bug report.
  53
  54 Contact
  55 -------
  56
  57 bugs@openvswitch.org
  58 http://openvswitch.org/