[reproducer] Pass libvirt layout to controller-0 for correct boot mode detection #3511
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
When generate_bm_info.yml runs on controller-0, it needs access to
_cifmw_libvirt_manager_layout to determine the correct boot_mode based
on the VM's uefi configuration. Since configure_controller.yml uses
delegate_facts: false, the layout fact wasn't available on controller-0,
causing boot_mode to always default to 'legacy' even for UEFI VMs.
This fix explicitly passes the layout from the hypervisor's hostvars
to make it available for the delegated tasks, ensuring VMs with nvram
are correctly identified as UEFI boot mode in baremetal-info.yml.
Also fixes the regex in reproducer/tasks/generate_bm_info.yml to set the
_type var and match hostnames that are like:
cifmw-compute-wcl4866c-0
Assisted-By: Claude
Jira: OSPRH-22373
Signed-off-by: James Slagle [email protected]