[ntpd] Update matching pattern of 'ERR ntpd' in loganalyzer ignore files

[wangxin]

Description of PR

Summary:
Fixes # (issue)
The ntpd may generate 'ERR ntpd' in syslog and caused unnecessary test
case failure. Previous PR #816
added a matching pattern of 'ERR ntpd' in loganalyzer igonre files to
ignore the ntpd error messages. However, ntpd may generate two formats
of error messages. The previously added matching pattern can only match
one of the formats. This change is to update the pattern to match both
of the formats.

Two formats of ntpd error message observed in testing:

Feb 26 20:23:29.807385 mtbc-sonic-03-2700 ERR ntpd[3816]: routing socket reports: No buffer space available
Apr 9 19:58:02.909960 mtbc-sonic-01-2410 ERR ntpd[12573]: message repeated 6 times: [ routing socket reports: No buffer space available]

Type of change

• Bug fix
• [] Testbed and Framework(new/improvement)
• [] Test case(new/improvement)

Approach

How did you do it?

Updated the matching pattern to match two formats of ntpd error messages.

How did you verify/test it?

Verified through python interactive shell.

>>> msg1 = "Feb 26 20:23:29.807385 mtbc-sonic-03-2700 ERR ntpd[3816]: routing socket reports: No buffer space available"
>>> msg2 = "Apr  9 19:58:02.909960 mtbc-sonic-01-2410 ERR ntpd[12573]: message repeated 6 times: [ routing socket reports: No buffer space available]"
>>> import re   
>>> pattern = re.compile(r".* ERR ntpd.*routing socket reports: No buffer space available.*")
>>> pattern.match(msg1)
<_sre.SRE_Match object at 0x7f35c73d87e8>
>>> pattern.match(msg2)
<_sre.SRE_Match object at 0x7f35c73d8850>

Any platform specific information?

No

Supported testbed topology if it's a new test case?

Documentation