Browse Source

Incorrect group name issue on non DPDK compute

This change is to fix the incorrect grouo name issue on non DPDK compute
node, currently pushes incorrect group 'hugetlbfs' to non DPDK node
instead of group 'qemu' when DPDK environment with 2 different roles
for compute nodes DPDK and non-DPDK.

Change-Id: I9462e0451b3be054568d951252fa7b1d3802c180
Closes-Bug: #1837034
(cherry picked from commit 76ee8f55fa)
changes/84/695084/1
Jaganathan Palanisamy 5 months ago
parent
commit
1f9a186793
1 changed files with 1 additions and 3 deletions
  1. +1
    -3
      puppet/services/neutron-ovs-dpdk-agent.yaml

+ 1
- 3
puppet/services/neutron-ovs-dpdk-agent.yaml View File

@@ -117,11 +117,9 @@ outputs:
- keys:
tripleo.neutron_ovs_agent.firewall_rules: tripleo.neutron_ovs_dpdk_agent.firewall_rules
- neutron::agents::ml2::ovs::enable_dpdk: true
- nova::compute::libvirt::qemu::group: {get_attr: [RoleParametersValue, value, vhostuser_socket_group]}
- get_attr: [Ovs, role_data, config_settings]
- get_attr: [RoleParametersValue, value]
service_config_settings:
nova_libvirt:
nova::compute::libvirt::qemu::group: {get_attr: [RoleParametersValue, value, vhostuser_socket_group]}
step_config: {get_attr: [NeutronOvsAgent, role_data, step_config]}
metadata_settings:
get_attr: [NeutronOvsAgent, role_data, metadata_settings]

Loading…
Cancel
Save