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

Test Plan: [RFE] OVS record/replay: support recording fatal signals

    • False
    • Hide

      None

      Show
      None
    • False
    • Hide

      ( ) The new test plan is aligned with the epic's acceptance criteria

      Given that an OVS daemon process is terminated by a fatal signal such as SIGINT or SIGTERM,

      When the ovs-appctl replay feature is used to record or replay daemon behavior,

      Then the record/replay system must correctly capture and reproduce the fatal signal termination event as part of the replay session.

      ( ) The test plan/test case pass successfully on all non blocking functions of the feature

      Show
      ( ) The new test plan is aligned with the epic's acceptance criteria Given that an OVS daemon process is terminated by a fatal signal such as SIGINT or SIGTERM, When the ovs-appctl replay feature is used to record or replay daemon behavior, Then the record/replay system must correctly capture and reproduce the fatal signal termination event as part of the replay session. ( ) The test plan/test case pass successfully on all non blocking functions of the feature
    • rhel-9
    • None
    • rhel-net-ovs-dpdk

      This task is tracking the test case writing activities to cover the feature request described below.

      Currently record/replay functionality can only record and replay
      a normal process exit (e.g. by the 'exit' appctl). But in real
      deployments it's normal for the process to be stopped by a signal
      (e.g. SIGINT or SIGTERM). We need to be able to record that and
      replay. OVS intercepts all fatal signals that can be intercepted,
      so recording should not be very hard to implement.

              ovsdpdk-triage ovsdpdk triage
              nstbot NST Bot
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated: