Bug 2053919
| Summary: | tuned.service fail to start at system startup | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Vasiliy Glazov <vascom2> |
| Component: | tuned | Assignee: | Jaroslav Škarvada <jskarvad> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 35 | CC: | jskarvad, olysonek-foss, pknirsch, vitaly |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | tuned-2.18.0-2.fc37 tuned-2.18.0-2.fc36 tuned-2.18.0-2.fc35 tuned-2.18.0-2.fc34 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2022-02-15 21:53:39 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
Vasiliy Glazov
2022-02-13 07:59:23 UTC
The problem is pre-installed and enabled by default since Fedora 35 power-profiles-daemon. Tuned is nonfunctional until power-profiles-daemon package is installed, because power-profiles-daemon.service has the following in its unit file: Conflicts=tuned.service tlp.service auto-cpufreq.service system76-power.service I think tuned should have `Conflicts=power-profiles-daemon.service` on systemd unit level and `Conflicts: power-profiles-daemon` on RPM SPEC level to force power-profiles-daemon removal. Pull request with fix: https://github.com/redhat-performance/tuned/pull/414 Thanks for the upstream PR. FEDORA-2022-bb243c40b4 has been submitted as an update to Fedora 37. https://bodhi.fedoraproject.org/updates/FEDORA-2022-bb243c40b4 FEDORA-2022-bb243c40b4 has been pushed to the Fedora 37 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-83c882c83f has been submitted as an update to Fedora 36. https://bodhi.fedoraproject.org/updates/FEDORA-2022-83c882c83f FEDORA-2022-83c882c83f has been pushed to the Fedora 36 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-c1f8c5a171 has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1f8c5a171 FEDORA-2022-a72c34927e has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-a72c34927e FEDORA-2022-c1f8c5a171 has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-c1f8c5a171` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-c1f8c5a171 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-a72c34927e has been pushed to the Fedora 34 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-a72c34927e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-a72c34927e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2022-c1f8c5a171 has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2022-a72c34927e has been pushed to the Fedora 34 stable repository. If problem still persists, please make note of it in this bug report. |