From e2f758d112e253ae00fbe93b5977b981c276f1ac Mon Sep 17 00:00:00 2001 From: Sergii Golovatiuk Date: Fri, 5 Dec 2025 13:10:34 +0100 Subject: [PATCH] [va-hci] Add compute VM variable defaults Define cifmw_libvirt_manager_compute_* variables explicitly to prevent template evaluation errors during fact gathering. When the scenario overrides cifmw_libvirt_manager_configuration, Ansible evaluates Jinja2 expressions before va-common.yml variables are in scope. Co-Authored-By: Claude Signed-off-by: Sergii Golovatiuk --- scenarios/reproducers/va-hci.yml | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/scenarios/reproducers/va-hci.yml b/scenarios/reproducers/va-hci.yml index ae40dc1f91..6a9ae7ce52 100644 --- a/scenarios/reproducers/va-hci.yml +++ b/scenarios/reproducers/va-hci.yml @@ -1,6 +1,12 @@ --- cifmw_parent_scenario: "scenarios/reproducers/va-hci-base.yml" +# Define compute VM settings (required when overriding cifmw_libvirt_manager_configuration) +cifmw_libvirt_manager_compute_amount: 3 +cifmw_libvirt_manager_compute_disksize: 50 +cifmw_libvirt_manager_compute_memory: 8 +cifmw_libvirt_manager_compute_cpus: 4 + # HERE if you want to override kustomization, you can uncomment this parameter # and push the data structure you want to apply. # cifmw_architecture_user_kustomize: