Reporting Bugs

Although every situation is different, this section describes how to collect data which will help make efficient use of everyone's time when dealing with vpp bugs.

FD.io's issue tracker can be found at GitHub

Before you press the GitHub button to create a bug report - or email vpp-dev@lists.fd.io - please ask yourself whether there's enough information for someone else to understand and to reproduce the issue given a reasonable amount of effort. Unicast emails to maintainers, committers, and the project PTL are strongly discouraged.

A good strategy for clear-cut bugs: file a detailed GitHub issue, and then send a short description of the issue to vpp-dev@lists.fd.io, perhaps from the issue description. It's fine to send email to vpp-dev@lists.fd.io to ask a few questions before filing issues.

• Data to include in bug reports
  • Image version and operating environment
  • "Show" command output
  • Network Topology
  • Packet Tracer Output
• Capturing post-mortem data
  • Syslog Output
  • Binary API Trace
  • Core Files
• Core files from Private Images
  • On-the-fly Core File Compression
  • Core File Summary