openstack/charm-nova-compute
Code Issues Proposed changes

Force config drive on s390x architecture

Browse Source 
When running on s390x force the use of config drive, this is because
on that architecture the DMI data won't be included in the libvirt's
domain definition, this will prevent cloud-init from knowing the
platform where the virtual machine is running on and it will default
to the config drive mechanism.

Change-Id: I74ecf45c8a7a127de2f903d6783473b45e6ea219
Closes-Bug: #2069607
Signed-off-by: Felipe Reyes <felipe.reyes@canonical.com>
This commit is contained in:
Felipe Reyes
2025-07-14 11:00:20 -04:00
parent 25a0aba59d
commit 7bc0ef9b57
1 changed files with 11 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files

11
templates/yoga/nova.conf
View File

@@ -117,6 +117,17 @@ volume_api_class = nova.volume.cinder.API
instances_path = {{ instances_path }}
{% endif -%}
{% if arch == 's390x' -%}
# When running on s390x force the use of config drive, this is because on that
# architecture the DMI data won't be included in the libvirt's domain
# definition, this will prevent cloud-init from knowing the platform where the
# virtual machine is running on and it will default to the config drive
# mechanism.
#
# More details at http://pad.lv/2069607
force_config_drive = True
{% endif -%}
{% if sections and 'DEFAULT' in sections -%}
{% for key, value in sections['DEFAULT'] -%}
{{ key }} = {{ value }}