Hey, Yeah, that's the patch you will need here. I have created the cherry-pick back to Wallaby / OSP17 now: https://review.opendev.org/c/openstack/tripleo-ansible/+/863794 So with that patch, you will need to specify that variable under the network_config dictionary in your baremetal_deployment.yaml file like so: - name: Compute count: 1 hostname_format: compute-%index% ansible_playbooks: - playbook: bm-deploy-playbook.yaml defaults: profile: compute-leaf2 networks: - network: internal_api subnet: internal_api_subnet02 - network: tenant subnet: tenant_subnet02 - network: storage subnet: storage_subnet02 network_config: template: templates/multiple_nics/multiple_nics_dvr.j2 num_dpdk_interface_rx_queues: 2. <<<---- Enter the number of queues you want here
Possible workaround: Run 'openstack overcloud node provision' without the '--network-config' option. Use a Heat environment file to define the nic-config template: parameter_defaults: ComputeOvsDpdkNetworkConfigTemplate: <path_to_template> NumDpdkInterfaceRxQueues: 4 Not using the '--network-config' option means that the network configuration will be applied later in the process when 'openstack overcloud deploy' run. When the stack has been created and config download deploy playbooks execute, node network config will be applied and the THT parameter `NumDpdkInterfaceRxQueues` can be used to control the desired setting in this case. NOTE: Make sure to set the <%ROLE%>NetworkConfigTemplate parameter for all roles, not only for ComputeOvsDpdk role since not using '--network-config' will apply to all roles.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Red Hat OpenStack Platform 17.0.1 bug fix and enhancement advisory), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2023:0271