CentOS Stream 10 – Common Problem 236 – Diagnosis and Fix

📖 ~1 min read

Table of contents

1. Symptom & Impact
2. Environment & Reproduction
3. Root Cause Analysis
4. Quick Triage
5. Step-by-Step Diagnosis
6. Solution – Primary Fix
7. Solution – Alternative Approaches
8. Verification & Acceptance Criteria
9. Rollback Plan
10. Prevention & Hardening
11. Related Errors & Cross-Refs
12. References & Further Reading

Symptom & Impact

Selected tuned profile is not applied after reboot, causing performance regression on workload nodes.

Environment & Reproduction

Happens when tuned service is masked, profile is mis-typed, or recommended profile is used by mistake.

Root Cause Analysis

tuned-adm only persists when the service is enabled and profile file exists under /etc/tuned/.

Quick Triage

Inspect systemctl status tuned and tuned-adm active versus tuned-adm recommend.

Step-by-Step Diagnosis

Run: systemctl status tuned; tuned-adm active; tuned-adm list.

Solution – Primary Fix

Run: sudo systemctl enable –now tuned; sudo tuned-adm profile ; reboot to verify.

Solution – Alternative Approaches

Use Ansible role tuned or write a custom profile in /etc/tuned//tuned.conf for repeatability.

Verification & Acceptance Criteria

tuned-adm active reports the expected profile after reboot and key kernel parameters match.

Rollback Plan

Switch back to virtual-guest or throughput-performance profile to revert workload settings.

Prevention & Hardening

Bake the tuned profile into image build pipelines and validate after every kernel upgrade.

Related Errors & Cross-Refs

Related to cpufreq governor, sysctl drift, and NUMA balancing problems.

Related tutorial: View the step-by-step tutorial for centos-stream-10.

View all centos-stream-10 tutorials on the Tutorials Hub →

Browse all common problems & solutions on the Tutorials Hub.

References & Further Reading

tuned-adm(8) and Red Hat performance tuning guide.