Bug 988696

Summary: Prompt FATAL to screen when change profile from spindown-disk to any one.
Product: Red Hat Enterprise Linux 6 Reporter: Longjun Song <lsong>
Component: ovirt-nodeAssignee: Fabian Deutsch <fdeutsch>
Status: CLOSED ERRATA QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 6.5CC: acathrow, bsarathy, cboyle, cshao, fdeutsch, jboggs, leiwang, ovirt-maint, tlavigne, yaniwang, ycui
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: ovirt-node-3.0.1-14.el6 Doc Type: Bug Fix
Doc Text:
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.
Story Points: ---
Clone Of: Environment:
These were generated by
Last Closed: 2014-01-21 19:46:56 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:
Bug Depends On:    
Bug Blocks: 1039985    
Attachments:
Description Flags
A snapshot about bug none

Description Longjun Song 2013-07-26 07:14:02 UTC
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:

Comment 2 Mike Burns 2013-07-26 12:10:42 UTC
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.

Comment 6 Cheryn Tan 2013-11-08 00:36:12 UTC
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.

Comment 7 Longjun Song 2013-11-08 05:18:57 UTC
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.

Comment 11 errata-xmlrpc 2014-01-21 19:46:56 UTC
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