qa-dev: Put tunnelip in connectivity results file

This makes the info readily available in the "Mesh Connectivity Results" section of the job, which is a lot easier than digging back into the previous step's log. Signed-off-by: Russell Bryant <[email protected]>
nexodus-io · Oct 1, 2023 · 2d596c8 · 2d596c8
1 parent 8e430f0
commit 2d596c8
Showing 1 changed file with 2 additions and 2 deletions.
diff --git a/ops/ansible/aws/validate-connectivity/tasks/main.yml b/ops/ansible/aws/validate-connectivity/tasks/main.yml
@@ -29,8 +29,8 @@
   become: yes
   shell: |
     printf "====== Connectivity Results from Node: {{ inventory_hostname }} ======\n" > {{ inventory_hostname }}-connectivity-results.txt
-    printf "IPv4 tunnel IP: "
-    nexctl nexd get tunnelip
+    printf "IPv4 tunnel IP: " >> {{ inventory_hostname }}-connectivity-results.txt
+    nexctl nexd get tunnelip >> {{ inventory_hostname }}-connectivity-results.txt
     nexctl nexd peers ping
     nexctl nexd peers ping >> {{ inventory_hostname }}-connectivity-results.txt 2>&1
     nexctl nexd peers ping6 >> {{ inventory_hostname }}-connectivity-results.txt 2>&1