Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

After provisioning a node getting error after scan.

Description

Seems to be happening with ip address with triple digits in the 1st segment. IP address like 23.x.x.x didn't get this error.

Error Message:
The Node with Id: 7; ForeignSource: EC2 Instances; ForeignId:1350340442439 has aborted for the following reason: Aborting node scan : Agent failed while scanning the IP address tables : Unexpected error occurred processing IP address tables for /174.129.203.196: java.lang.IllegalArgumentException: Invalid IPAddress [B@424457a0 with length 20

Environment

Fedora 17/Amazon AWS instance

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Equipe Equipe July 16, 2013 at 2:55 AM

Can someone confirm that the fix is integrated in Version 1.10.10 and later ?

Eric Kreckel March 29, 2013 at 12:43 PM

Excellent and thank you. Glad I was able to spur the resolution.

Benjamin Reed March 29, 2013 at 12:35 PM

Actually, I've committed a fix, the issue was that in the table tracker; we're accepting address types 3 (IPv4 + zone) and 4 (IPv6 + zone) but not actually handling them properly before padding them to InetAddressUtils.

It's in the 1.10 branch and higher.

Let me know if that doesn't work for you, but I think it should.

Eric Kreckel March 28, 2013 at 9:44 PM

I can get you an SNMP walk. Please let me know the OID you would like me to start from.

Benjamin Reed March 28, 2013 at 9:27 PM

Looking at the code, it seems the real fix should not be in InetAddressUtils, since you should only be passing the right-length array to that in the first place. If you look at the table tracker code, it should, in theory, be already pulling the index out before even getting to that code.

Do you have an snmpwalk we could use to reproduce this in a unit test?

Fixed

Details

Assignee

Reporter

Components

Fix versions

Affects versions

Priority

PagerDuty

Created October 16, 2012 at 11:06 AM
Updated January 27, 2017 at 4:21 PM
Resolved March 29, 2013 at 12:35 PM

Flag notifications