From 62fc1e79ddaf7144c2979cc3caeb9a8cc91701c2 Mon Sep 17 00:00:00 2001 From: Jack Hodgkiss Date: Thu, 18 Apr 2024 12:29:37 +0100 Subject: [PATCH] fix: conditional error when no seed exists In situations where there is no `seed` the `seed-hypervisor` will fail a host configure against `no_proxy` settings due to the conditional attempting to access attributes that do not exist. --- .../inventory/group_vars/seed-hypervisor/proxy.yml | 12 ++++++++++++ 1 file changed, 12 insertions(+) create mode 100644 etc/kayobe/inventory/group_vars/seed-hypervisor/proxy.yml diff --git a/etc/kayobe/inventory/group_vars/seed-hypervisor/proxy.yml b/etc/kayobe/inventory/group_vars/seed-hypervisor/proxy.yml new file mode 100644 index 000000000..e04404c5b --- /dev/null +++ b/etc/kayobe/inventory/group_vars/seed-hypervisor/proxy.yml @@ -0,0 +1,12 @@ +--- +############################################################################### +# Configuration of HTTP(S) proxies. + +# The default value whilst only applied if `http_proxy` and `https_proxy` are set +# will not work as the conditional fails to evaluate if the seed node does not exist. +# This makes the `seed-hypervisor` reliant on the seed node. +no_proxy: [] + +############################################################################### +# Dummy variable to allow Ansible to accept this file. +workaround_ansible_issue_8743: yes