Skip to:

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

NPE in IpInterfaceScan when processing IPLike rule with IPv6 address

Description

The following error message was found in provisiond.log:

This occurred while running snapshots from release-19.0.0, but I suspect that older versions are affected too.

Acceptance / Success Criteria

None

Lucidchart Diagrams

Activity

Show:

Ronny Trommer February 14, 2017 at 9:57 AM

you can even try

fooker February 14, 2017 at 7:59 AM

fooker February 8, 2017 at 11:09 AM

Does this also happen in the IPLike stored procedure?

fooker February 8, 2017 at 8:59 AM
Edited

A similar expansion mechanism exists for IPv4, too: i.E. ping 127.1.

Alejandro Galue December 6, 2016 at 12:55 PM

That's the idea, you can add a logic or to match both cases. Although, the IPv6 expressions doesn't support "auto-expand", so ::1 won't work, it should be 0:0:0:0:0:0:0:1. Of course, it would be a nice feature to add to IPLike for IPv6.

Fixed

Details

Assignee

Reporter

Components

Sprint

Fix versions

Affects versions

Priority

PagerDuty

Created December 5, 2016 at 10:38 AM
Updated February 15, 2018 at 8:56 PM
Resolved February 17, 2017 at 10:39 AM