Bug 1392942 - tuned-adm profile NONEXISTENT returns to the shell after timeout
Summary: tuned-adm profile NONEXISTENT returns to the shell after timeout
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: tuned
Version: 7.3
Hardware: Unspecified
OS: Unspecified
high
unspecified
Target Milestone: rc
: ---
Assignee: Jaroslav Škarvada
QA Contact: Tereza Cerna
URL:
Whiteboard:
Depends On: 1369502
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-11-08 14:01 UTC by Marcel Kolaja
Modified: 2016-12-06 17:12 UTC (History)
8 users (show)

Fixed In Version: tuned-2.7.1-3.el7_3.1
Doc Type: Bug Fix
Doc Text:
Previously,the tuned-adm profile NONEXISTENT returned to the shell after timeout, which blocked the execution of oVirt. With the fix, it returns to the shell immediately.
Clone Of: 1369502
Environment:
Last Closed: 2016-12-06 17:12:13 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2886 0 normal SHIPPED_LIVE tuned bug fix update 2016-12-06 22:01:46 UTC

Description Marcel Kolaja 2016-11-08 14:01:21 UTC 
This bug has been copied from bug #1369502 and has been proposed
to be backported to 7.3 z-stream (EUS).
Comment 4 Tereza Cerna 2016-11-09 08:49:03 UTC 
================================
Verified in:
    tuned-2.7.1-3.el7_3.1.noarch
PASS
================================

# tuned-adm profile nonexistent
Requested profile 'nonexistent' doesn't exist.
# echo $?
1
#

================================
Reproduced in:
    tuned-2.7.1-3.el7.noarch
FAIL
================================

# tuned-adm profile nonexistent
Requested profile 'nonexistent' doesn't exist.
Operation timed out after waiting 600 seconds(s), you may try to increase timeout by using --timeout command line option or using --async.
# echo $?
1
Comment 6 errata-xmlrpc 2016-12-06 17:12:13 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.

https://rhn.redhat.com/errata/RHBA-2016-2886.html
Note You need to log in before you can comment on or make changes to this bug.