Bug 2176029 - Specifying tuned profile "virtual-host" during node provision is failing in playbook cli-overcloud-node-kernelargs.yaml [NEEDINFO]
Summary: Specifying tuned profile "virtual-host" during node provision is failing in p...
Keywords:
Status: ASSIGNED
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: documentation
Version: 17.1 (Wallaby)
Hardware: Unspecified
OS: Unspecified
low
low
Target Milestone: ---
: ---
Assignee: RHOS Documentation Team
QA Contact: RHOS Documentation Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-03-07 08:18 UTC by Vijayalakshmi Candappa
Modified: 2023-08-08 11:27 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Release Note
Doc Text:
Clone Of:
Environment:
Last Closed:
Target Upstream Version:
Embargoed:
vcandapp: needinfo? (jamsmith)


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker NFV-2831 0 None None None 2023-04-20 05:33:56 UTC
Red Hat Issue Tracker OSP-22941 0 None None None 2023-03-07 08:19:37 UTC

Description Vijayalakshmi Candappa 2023-03-07 08:18:04 UTC
Description of problem:
1. Trying to deploy computevpda role, with tuned profile set to "virtual-host" in the baremetal deployment file:
Eg. 
  ansible_playbooks:
    - playbook: /usr/share/ansible/tripleo-playbooks/cli-overcloud-node-kernelargs.yaml
      extra_vars:
        kernel_args: "default_hugepagesz=1GB hugepagesz=1G hugepages=64 iommu=pt intel_iommu=on tsx=off isolcpus=2-19,22-39"
        reboot_wait_timeout: 900
        tuned_profile: "virtual-host"

2. Run node provision command
3. The playbook fails at:

- name: Fail if tuned profile conf is absent but isolated cores is provided
  fail:
    msg: "Tuned profile conf file is not available to configure isolated cores"
  when:
    - tuned_isolated_cores is defined
    - (tuned_isolated_cores | length) > 0
    - not (tuned_conf_stat_result.stat.exists | bool)

Version-Release number of selected component (if applicable):
OSP17.x

How reproducible:
Always

Steps to Reproduce:
1. Try to configure node with some other tuned profile like "virtual-host"
2. Do node provision
3.

Actual results:
Node provision / deploy fails

Expected results:
Node should be provisioned with user-specified tuned profile

Additional info:

Comment 3 James Slagle 2023-03-07 17:06:23 UTC
It does check for mandatory parameters, that's partly what that task is checking.
The /etc/tuned/{{ tuned_profile }}-variables.conf file doesn't exist, which is the other check. You would have to set tuned_isolated_cores:"" to get past this check.

Comment 4 James Slagle 2023-03-07 17:12:20 UTC
What provides the virtual-host tuned profile?


Note You need to log in before you can comment on or make changes to this bug.