Bug 1500207 - [R39yiZs4] Failed to parse max ARP entries errors appear in the node log
Summary: [R39yiZs4] Failed to parse max ARP entries errors appear in the node log
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 3.7.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.8.0
Assignee: Dan Williams
QA Contact: Meng Bo
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-10 08:10 UTC by Meng Bo
Modified: 2018-03-28 14:07 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-03-28 14:07:14 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:07:53 UTC

Description Meng Bo 2017-10-10 08:10:12 UTC
Description of problem:
As subject, error log:
Oct 10 07:56:45 qe-bmeng-37-node-registry-router-1.localdomain atomic-openshift-node[10500]: E1010 07:56:45.458893   10509 metrics.go:172] failed to parse max ARP entries "512\n" for metrics: *strconv.NumError strconv.Atoi: parsing "512\n": invalid syntax


Version-Release number of selected component (if applicable):
v3.7.0-0.143.1

How reproducible:
always

Steps to Reproduce:
1. Setup OCP env with metrics enabled
2. Check the node log
3.

Actual results:
Some errors about max ARP entries appear in the node log.

Expected results:
Should not show such errors.

Additional info:

Comment 1 Dan Winship 2017-10-10 16:18:42 UTC
fixed by https://github.com/openshift/origin/pull/16518

Comment 2 Dan Winship 2017-10-10 16:19:44 UTC
sorry, no, it was *caused* by that, it's fixed by https://github.com/openshift/origin/pull/16661

Comment 3 Meng Bo 2017-10-17 08:41:45 UTC
Tested on build v3.7.0-0.157.0, no such error in node log.

Verify this bug.

Comment 6 errata-xmlrpc 2018-03-28 14:07:14 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://access.redhat.com/errata/RHBA-2018:0489


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