Bug 1226525 - Cockpit confusing behavior with performance profiles
Summary: Cockpit confusing behavior with performance profiles
Status: IN_PROGRESS
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: Cockpit (show other bugs)
Version: Current
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Alice Brooks
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-06-19 12:24 UTC by Robert Simai
Modified: 2024-07-12 07:48 UTC (History)
2 users (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Robert Simai 2024-06-19 12:24:40 UTC
Fresh boot, log into Cockpit as regular user, see Overview, Configuration, "Performance profile: none". Mouse over "none" shows "Tuned is not running". All correct so far.

Switch to administrative access, still it shows "Performance profile none" but isn't grayed out anymore. Click on that gives an error

-->--
Change performance profile
Danger alert:Server has closed the connection.
-<--

which makes sense, as tuned is not running.

But after clicking the error away the performance profile ("virtual-guest" in my installation) shows correctly and can be changed. Tuned is still disabled but now running, Cockpit magically started it.

Changing the profile finally changes tuned to be enabled for system boot, again magically and without telling the admin. This is confusing.

I suggest to change the error to something understandable, maybe along with adding something meaningful to the docs.
Comment 1 Alice Brooks 2024-07-12 07:48:14 UTC
Submitted a pr to fix this here: https://github.com/cockpit-project/cockpit/pull/20748