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.

Description of problem:
RHEL 6.3 - running sosreport generates a warning about sysctl 

process `sosreport' is using deprecated sysctl (syscall) net.ipv6.neigh.default.retrans_time; Use net.ipv6.neigh.default.retrans_time_ms instead.


Version-Release number of selected component (if applicable):

sos-2.2-29.el6.noarch

How reproducible:
always


Steps to Reproduce:
1. run sosreport
2.
3.
  
Actual results:


Expected results:


Additional info:

Thanks for the report - these two are strict synonyms (if you modify one the change is reflected in the other) so there is no loss of diagnostic data if we switch to retrans_time_ms.

We're working on changing proc and sys collection upstream (should land in F18) to support blacklists which would handle this case.

For now I'll look at adding a forbidden path for this specific sysctl (and also do a grep on RHEL6 kernel git to see if we have any others needing this treatment).

(confirming the reproducibility, just hit this exact instance)

The warning message can be found in syslog sink (/var/log/messages)
with kernel as its origin.

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-2013-0474.html