Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2267243

Summary:	[OSP17.1] ComputeCPUPinning documentation misses requirement for TunedProfileName
Product:	Red Hat OpenStack	Reporter:	Rafal Szmigiel <rszmigie>
Component:	documentation	Assignee:	Joanne O'Flynn <joflynn>
Status:	CLOSED MIGRATED	QA Contact:	RHOS Documentation Team <rhos-docs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	17.1 (Wallaby)	CC:	astupnik, bgibizer, mariel
Target Milestone:	---	Keywords:	Triaged
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2025-01-28 16:53:26 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Rafal Szmigiel 2024-03-01 13:49:16 UTC

Description of problem:
While following docs https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html/configuring_the_compute_service_for_instance_creation/assembly_configuring-cpus-on-compute-nodes#proc_configuring-compute-nodes-for-cpu-pinning_cpu-pinning to configure Compute nodes for CPU pinning, I have found that there is missing requirement to configure

    TunedProfileName: "cpu-partitioning"

Please see: https://access.redhat.com/solutions/7008189

Without cpu-partitioning tuned profile enabled deployment will fail as Ansible checks for it in the following task: "Fail if tuned profile conf is absent but isolated cores is provided"

Could we please ensure that requirement for cpu-partitioning tuned profile is explicitly listed under the above document, similarly to how is it done with guide to configure OSP for NFV workloads please?

(For an instance: https://access.redhat.com/documentation/en-us/red_hat_openstack_platform/17.1/html-single/configuring_network_functions_virtualization/index)


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 Joanne O'Flynn 2025-01-28 16:53:26 UTC

Follow Jira for updates.