Uploaded image for project: 'Fast Datapath Product'
  1. Fast Datapath Product
  2. FDP-461

More informative error messages on 'execute'/'flow_{put/get/del}' actions.

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • ovs-dpdk
    • None
    • More informative error messages on 'execute'/'flow_{put/get/del}' actions.
    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      Please mark each item below with ( / ) if completed or ( x ) if incomplete:

      ( ) The acceptance criteria defined below are met.

      ( ) The epics work is available in a downstream build (nightly/async or other)

      ( ) Test coverage is available in downstream CI if applicable

      ( ) All cards under the epic have been moved to Done

      ( ) Failed Test Plans have bugs added as children to the epic/feature.

      Show
      Please mark each item below with ( / ) if completed or ( x ) if incomplete: ( ) The acceptance criteria defined below are met. ( ) The epics work is available in a downstream build (nightly/async or other) ( ) Test coverage is available in downstream CI if applicable ( ) All cards under the epic have been moved to Done ( ) Failed Test Plans have bugs added as children to the epic/feature.
    • rhel-net-ovs-dpdk
    • 100% To Do, 0% In Progress, 0% Done
    • ssg_networking

      This epic tracks all the effort needed to deliver the solution related to the feature request described below.
      Old ticket: https://bugzilla.redhat.com/show_bug.cgi?id=1944144

      --8<--
      Get the error string from the kernel in a netlink reply, not just an errno. "Invalid argument" is not useful at all if we have no idea which of the dozen flow matches and actions was rejected by kernel.

      Maybe we use netlink ext ack for this? The out of tree module has some of this already.

      Talk to Ilya to get more details.
      --8<--
      See also
      BZ2059162
      which is a duplicate of this BZ:

      We recently added to OVS support to actually print extended ack
      messages received from the kernel:
      https://github.com/openvswitch/ovs/commit/4a6a4734622e42367faf39cd3938bc8a57786282
      but I'm not sure if anyone started to add more messages to the kernel
      itself.

      In general, we need to find all the places where execute/put/get/del
      requests returns an error inside the kernel and add some meaningful
      extack message to the netlink reply at that point. It's kind of a
      lot of work, but it should be very beneficial for anyone who tries
      to debug this kind of in-kernel problem or miscommunication between
      OVS kernel and userspace.

              ovsdpdk-bot ovsdpdk bot
              echaudro@redhat.com Eelco Chaudron
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: