[METRON-647] Parser unit test failures due to assumed year values

• Type: Bug
• Status: Done
• Priority: Blocker
• Resolution: Done
• Fix Version/s: 0.3.1
• Assignee: Justin Leet
• Reporter: Kyle Richardson
• Created: 03/Jan/17 21:08
• Updated: 26/Jan/17 22:45
• Resolved: 04/Jan/17 17:26

Description

Unit Tests Failing:

• BasicAsaParserTest.testIp6Addr:151
• GrokWebSphereParserTest.testParseLoginLine:60
• GrokWebSphereParserTest.testParseMalformedLoginLine:151
• GrokWebSphereParserTest.tetsParseLogoutLine:84
• GrokWebSphereParserTest.tetsParseMalformedLogoutLine:175
• GrokWebSphereParserTest.tetsParseMalformedOtherLine:220
• GrokWebSphereParserTest.tetsParseMalformedRBMLine:198
• GrokWebSphereParserTest.tetsParseOtherLine:129
• GrokWebSphereParserTest.tetsParseRBMLine:107

The issue appears to be the same for all. The original syslog message did not include a year (fairly common); however, we have hard coded an assertion based on the year the code was written (in our case 2016).

Issue Links

• is duplicated by: METRON-648 GrokWebSphereParserTest and BasicAsaParserTest are not 2017-safe
• links to: GitHub Pull Request #412