tests: openvswitch: Wait for 'openvswitch-configuration' to be up.

Checking for "br0" should only be done once the
'openvswitch-configuration' service is up because it's the one that sets
it up.

* gnu/tests/networking.scm (run-openvswitch-test)["openvswitch-configuration
is running"]: New test.

1 files changed, 9 insertions, 1 deletions

diff --git a/gnu/tests/networking.scm b/gnu/tests/networking.scm
index 3f3f653b8a4..a8358c6a555 100644
--- a/gnu/tests/networking.scm
+++ b/gnu/tests/networking.scm
@@ -4,7 +4,7 @@
 ;;; Copyright © 2018 Chris Marusich <cmmarusich@gmail.com>
 ;;; Copyright © 2018 Arun Isaac <arunisaac@systemreboot.net>
 ;;; Copyright © 2021 Maxime Devos <maximedevos@telenet.be>
-;;; Copyright © 2021 Ludovic Courtès <ludo@gnu.org>
+;;; Copyright © 2021, 2023 Ludovic Courtès <ludo@gnu.org>
 ;;;
 ;;; This file is part of GNU Guix.
 ;;;
@@ -300,6 +300,14 @@ port 7, and a dict service on port 2628."
           (test-runner-current (system-test-runner #$output))
           (test-begin "openvswitch")
 
+          ;; Wait for our configuration to be active (it sets up br0).
+          (test-assert "openvswitch-configuration is running"
+            (marionette-eval
+             '(begin
+                (use-modules (gnu services herd))
+                (wait-for-service 'openvswitch-configuration))
+             marionette))
+
           ;; Make sure the bridge is created.
           (test-assert "br0 exists"
             (marionette-eval