Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1219852

Summary:	Upgrade trace-cmd to at least 2.2.4 and possibly to 2.5.x
Product:	Red Hat Enterprise Linux 7	Reporter:	John Kacur <jkacur>
Component:	trace-cmd	Assignee:	John Kacur <jkacur>
Status:	CLOSED ERRATA	QA Contact:	Ziqian SUN (Zamir) <zsun>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	7.3	CC:	bhu, lilu
Target Milestone:	rc
Target Release:	7.3
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:	Cause: Need to upgrade version of trace-cmd Consequence: Not all features and fixes available to customer Fix: Upgrade to trace-cmd-2.6.0 Result: The customer has the latest code, and it is easier for upstream maintainers to work with.	Story Points:	---
Clone Of:
Clones:	1365951 (view as bug list)		Environment:
Last Closed:	2016-11-04 08:07:12 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:	1274397, 1282960

Description John Kacur 2015-05-08 13:27:58 UTC

Description of problem:

We should either upgrade to 2.2.4 or to 2.5.x

Either one of these are minor version upgrades
Both contain a number of fixes that we should apply.

2.5.x would be preferable. This is also incremental, but is more likely to be supported for back-porting patches.

Comment 1 John Kacur 2016-06-27 14:49:33 UTC

Upgraded to trace-cmd-2.6.0
Complete in trace-cmd-2.6.0-2.el7 and up

Comment 5 errata-xmlrpc 2016-11-04 08:07:12 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-2531.html