Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
When switching profile from spindown-disk to any other profile,the system would generate a series of error messages, for example: "/etc/tune-profiles/functions: line22: echo: write error: Invalid argument". These were invalid messages as the profiles were still switched. This has been modified so these error messages no longer appear.
Created attachment 778688[details]
A snapshot about bug
Description of problem:
Switch profile from spindown-disk to any other profiles, it will say:
/etc/tune-profiles/functions: line22: echo: write error: Invalid argument
/etc/tune-profiles/functions: line22: echo: write error: Invalid argument
/etc/tune-profiles/functions: line22: echo: write error: Invalid argument
/etc/tune-profiles/functions: line22: echo: write error: Invalid argument
/etc/tune-profiles/functions: line22: echo: write error: Invalid argument
WARNING: Could not open '/lib/modules/2.6.32-398.el6.x86_64/kernel/net/rfkill/rfkill.ko': No such file or directory
WARNING: Could not open '/lib/modules/2.6.32-398.el6.x86_64/kernel/net/bluetooth/bluetooth.ko': No such file or directory
FATAL: Could not open '/lib/modules/2.6.32-398.el6.x86_64/kernel/drivers/bluetooth/btusb.ko': No such file or directory
Version-Release number of selected component (if applicable):
RHEV Hypervisor 6.5-20130725.0.el6
How reproducible:
100%
Steps to Reproduce:
1. Select Performance tab then choose the spindown-disk profile.
2. Change the current profile to any other profile, it will show this error
Actual results:
Expected results:
Fabian, can you see if we can simply catch the output and hide it? The errors are for kernel modules that we don't care about (bluetooth). Looking at the output after the error, the profile does get successfully switched.
This bug is currently attached to errata RHBA-2013:15277. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
https://bugzilla.redhat.com/page.cgi?id=fields.html#cf_release_notes
Thanks in advance.
This problem is still existed in RHEVH Hypervisor 6.5-20131031.1
Steps:
1. Clean install RHEVH Hypervisor 6.5-20131031.1 from any media
2. Switch to the Performance tab and set the current active profile to spindown-disk
3. Change the current profile to any other profiles
4. The bug is still there.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
http://rhn.redhat.com/errata/RHBA-2014-0033.html
Created attachment 778688 [details] A snapshot about bug Description of problem: Switch profile from spindown-disk to any other profiles, it will say: /etc/tune-profiles/functions: line22: echo: write error: Invalid argument /etc/tune-profiles/functions: line22: echo: write error: Invalid argument /etc/tune-profiles/functions: line22: echo: write error: Invalid argument /etc/tune-profiles/functions: line22: echo: write error: Invalid argument /etc/tune-profiles/functions: line22: echo: write error: Invalid argument WARNING: Could not open '/lib/modules/2.6.32-398.el6.x86_64/kernel/net/rfkill/rfkill.ko': No such file or directory WARNING: Could not open '/lib/modules/2.6.32-398.el6.x86_64/kernel/net/bluetooth/bluetooth.ko': No such file or directory FATAL: Could not open '/lib/modules/2.6.32-398.el6.x86_64/kernel/drivers/bluetooth/btusb.ko': No such file or directory Version-Release number of selected component (if applicable): RHEV Hypervisor 6.5-20130725.0.el6 How reproducible: 100% Steps to Reproduce: 1. Select Performance tab then choose the spindown-disk profile. 2. Change the current profile to any other profile, it will show this error Actual results: Expected results: