infrastructure-playbooks: add comments for lv_vars.yml

Add comments telling user that devices used in
playbooks must not have GPT/FS/RAID signatures

Signed-off-by: Ali Maredia <amaredia@redhat.com>

diff --git a/infrastructure-playbooks/vars/lv_vars.yaml b/infrastructure-playbooks/vars/lv_vars.yaml
index 3a7439aa39cf248285f721372413cd875341cc0b..314e0eafa75db88a2e6b4657ca83b1c71cfa9ff3 100644 (file)
--- a/infrastructure-playbooks/vars/lv_vars.yaml
+++ b/infrastructure-playbooks/vars/lv_vars.yaml
@@ -4,6 +4,12 @@
 # The LVs for journals are created first then the LVs for data. All LVs for journals correspond to a LV for data.
 #
 ## CHANGE THESE VARS ##
+#
+# The NVMe device and the hdd devices must be raw and not have any GPT, FS, or RAID signatures. 
+# GPT, FS, & RAID signatures should be removed from a device prior to running the lv-create.yml playbook. 
+# 
+# Having leftover signatures can result in ansible errors that say "device $device_name excluded by a filter" after running the lv-create.yml playbook.
+# This can be done by running `wipefs -a $device_name`.
 
 # Path of nvme device primed for LV creation for journals and data. Only one NVMe device is allowed at a time. Providing a list will not work in this case.
 nvme_device: /dev/nvme0n1