tests: Fix connect_cmd_roam with old scan results

connect_cmd_roam did not force a new scan to find the second AP. This
could result in failures due to the ROAM command getting rejected, e.g.,
in the following test case sequence: wext_pmksa_cache connect_cmd_roam.

Signed-off-by: Jouni Malinen <j@w1.fi>

diff --git a/tests/hwsim/test_connect_cmd.py b/tests/hwsim/test_connect_cmd.py
index 3f4c42b4f2fa513aca8de101922155b75d6c53e6..5b528a6ded75c967bca00d8814319f62eddc0fe6 100644 (file)
--- a/tests/hwsim/test_connect_cmd.py
+++ b/tests/hwsim/test_connect_cmd.py
@@ -149,5 +149,5 @@ def test_connect_cmd_roam(dev, apdev):
     wpas.connect("sta-connect", key_mgmt="NONE", scan_freq="2412")
 
     hostapd.add_ap(apdev[1]['ifname'], params)
-    wpas.scan_for_bss(apdev[1]['bssid'], freq=2412)
+    wpas.scan_for_bss(apdev[1]['bssid'], freq=2412, force_scan=True)
     wpas.roam(apdev[1]['bssid'])