ansible: create a node_wandboard group

Move the reboot on readonly root action to this new group as it doesn't
apply to the new armhf containers.

Change-Id: I9b91a7e30614c920bf54593edd8601b59816c7d6
Signed-off-by: Michael Jeanson <mjeanson@efficios.com>

diff --git a/automation/ansible/group_vars/node_armhf.yml b/automation/ansible/group_vars/node_armhf.yml
deleted file mode 100644 (file)
index 27c2931..0000000
--- a/automation/ansible/group_vars/node_armhf.yml
+++ /dev/null
@@ -1,6 +0,0 @@
----
-# The SATA controllers on the boards that are running the armhf
-# nodes are somewhat flaky, and the root filesystem often ends
-# up readonly due to errors. When the FS goes read-only, jobs
-# will fail so the easiest action is to have the node reboot.
-common_node_rootfs_readonly_reboot: true

diff --git a/automation/ansible/group_vars/node_wandboard.yml b/automation/ansible/group_vars/node_wandboard.yml
new file mode 100644 (file)
index 0000000..27c2931
--- /dev/null
+++ b/automation/ansible/group_vars/node_wandboard.yml
@@ -0,0 +1,6 @@
+---
+# The SATA controllers on the boards that are running the armhf
+# nodes are somewhat flaky, and the root filesystem often ends
+# up readonly due to errors. When the FS goes read-only, jobs
+# will fail so the easiest action is to have the node reboot.
+common_node_rootfs_readonly_reboot: true

diff --git a/automation/ansible/hosts b/automation/ansible/hosts
index 793f4a45720c981267ec9852bc73c1714d2dd0d9..5e5b771bfb2317df5bb3f4da083318ff7dc6efe6 100644 (file)
--- a/automation/ansible/hosts
+++ b/automation/ansible/hosts
@@ -33,6 +33,9 @@ ci-host-win11-arm64-01.internal.efficios.com
 [infra_lava]
 lava-master-03.internal.efficios.com
 
+[node_wandboard]
+ci-node-deb12-armhf-[01:08]
+
 [node_armhf]
 ci-node-deb12-armhf-01
 ci-node-deb12-armhf-02