Fix: OSPF "passive interface" tests have to reset OSPF on probes first

The OSPF "passive interface" tests rely on one of the probes not having
an OSPF neighbor. With the new FRR configuration process, FRR gets
ready way before the tested device and remembers any brain fart the
tested device makes. Clearing the OSPF process before starting the test
ensures a clean slate.

Author: ipspace

tests/integration/ospf/ospfv2/04-passive.yml

@@ -42,10 +42,11 @@ links:
   mtu: 1500
 
 validate:
-  clear_x2:
+  reset_ospf:
     description: Cleanup after leaky OSPFv2 implementations (IOS XR)
-    nodes: [ x2 ]
-    exec.frr: vtysh -c 'clear ip ospf neighbor'
+    nodes: [ x1, x2 ]
+    exec.frr: >-
+      vtysh -c 'clear ip ospf process'
   adj_x1:
     description: Is DUT a neigbor of X1?
     wait: ospfv2_adj_p2p

tests/integration/ospf/ospfv3/04-passive.yml

@@ -42,6 +42,11 @@ links:
   mtu: 1500
 
 validate:
+  reset_ospf:
+    description: Cleanup after leaky OSPFv3 implementations
+    nodes: [ x1, x2 ]
+    exec.frr: >-
+      vtysh -c 'clear ipv6 ospf6 process'
   adj_x1:
     description: Is DUT a neigbor of X1?
     wait: ospfv3_adj_p2p