T2-VOQ-VS: Add command to loganalyzer ignore

[deepak-singhal0408]

Description of PR

Summary:
As part of T2-VS Support changes(sonic-net/sonic-buildimage#18512), sonic_platform package will be available now on VS platforms.
sfputil script was getting exited earlier due to module not found. But now, the module will be found, and next it invokes load_platform_chassis(). For non-chassis VS platforms, the metadata file will not be present, and hence it throws an exception with a syslog.
ERR sfputil: Failed to instantiate Chassis due to FileNotFoundError('Metadata file /etc/sonic/vs_chassis_metadata.json not found')

The sonic-mgmt tests on VS which invoke sfputil commands are failing with loganalyzer caching this message.

Fix: Adding the above to loganalyzer ignore messages.

Type of change

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

Back port request

• 201911
• 202012
• 202205
• 202305
• 202311

Approach

What is the motivation for this PR?

As part of T2-VS Support changes, sonic_platform package will be available now on VS platforms.
sfputil script was getting exited earlier due to module not found. But now, the module will be found, and next it invokes load_platform_chassis(). For non-chassis VS platforms, the metadata file will not be present, and hence it throws an exception with a syslog.
ERR sfputil: Failed to instantiate Chassis due to FileNotFoundError('Metadata file /etc/sonic/vs_chassis_metadata.json not found')

How did you do it?

Added the above to loganalyzer ignore messages.

How did you verify/test it?

Any platform specific information?

None

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

None

Documentation

[deepak-singhal0408]

@judyjoseph , could you please help review/merge this PR?

[saiarcot895]

This isn't actually matching the syslog message because there's a space before Metadata here, but that space isn't in the actual log message.

[deepak-singhal0408]

This isn't actually matching the syslog message because there's a space before Metadata here, but that space isn't in the actual log message.

yes.. realized this.. will fix it today.. thanks for pointing out.