test/suites: Test storage/network can be specified when targetting cl…

…uster group. Signed-off-by: Mark Laing <[email protected]>
canonical · Nov 8, 2024 · 0111b79 · 0111b79
1 parent 05f6d56
commit 0111b79
Showing 1 changed file with 4 additions and 4 deletions.
diff --git a/test/suites/clustering.sh b/test/suites/clustering.sh
@@ -3660,12 +3660,12 @@ EOF
   lxc init testimage cluster:c1
   lxc info cluster:c1 | grep -q "Location: node1"
 
-  # c2 should go to node2
-  lxc init testimage cluster:c2 --target=@blah
+  # c2 should go to node2. Additionally it should be possible to specify the network.
+  lxc init testimage cluster:c2 --target=@blah --network "${bridge}"
   lxc info cluster:c2 | grep -q "Location: node2"
 
-  # c3 should go to node2 again
-  lxc init testimage cluster:c3 --target=@blah
+  # c3 should go to node2 again. Additionally it should be possible to specify the storage pool.
+  lxc init testimage cluster:c3 --target=@blah --storage data
   lxc info cluster:c3 | grep -q "Location: node2"
 
   # Direct targeting of node2 should work