Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 1560965 - net-snmp leak patch backport from https://sourceforge.net/p/net-snmp/code/ci/9bce2c951 [rhel-7.5.z]
net-snmp leak patch backport from https://sourceforge.net/p/net-snmp/code/ci/...
Status: CLOSED ERRATA
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: net-snmp (Show other bugs)
7.4
All Linux
urgent Severity high
: rc
: ---
Assigned To: Josef Ridky
Stanislav Zidek
Ioanna Gkioka
: Patch, Reproducer, ZStream
Depends On: 1533780
Blocks:
  Show dependency treegraph
 
Reported: 2018-03-27 07:21 EDT by Oneata Mircea Teodor
Modified: 2018-05-14 12:10 EDT (History)
9 users (show)

See Also:
Fixed In Version: net-snmp-5.7.2-33.el7_5.1
Doc Type: Bug Fix
Doc Text:
Previously, a memory leak occurred during the snmpd process. Consequently, the amount of consumed memory continued to grow over time. This bug has been fixed, and the net-snmp packages no longer leak memory.
Story Points: ---
Clone Of: 1533780
Environment:
Last Closed: 2018-05-14 12:10:02 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:1382 None None None 2018-05-14 12:10 EDT

  None (edit)
Description Oneata Mircea Teodor 2018-03-27 07:21:02 EDT
This bug has been copied from bug #1533780 and has been proposed to be backported to 7.5 z-stream (EUS).
Comment 10 errata-xmlrpc 2018-05-14 12:10:02 EDT
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://access.redhat.com/errata/RHBA-2018:1382

Note You need to log in before you can comment on or make changes to this bug.