search

sonic-net / sonic-buildimage

Scripts which perform an installable binary image build for SONiC
Other
722 stars 1.38k forks source link

Unknown log level appear for JINJA2_CACHE when running swssloglevel -p command #12140

Closed dprital closed 1 year ago

dprital commented 1 year ago

Description

When running "swssloglevel -p" command that suppose to present the log level set per each component,
The first component appear is "JINJA2_CACHE" (as it is part of LOGLEVEL_DB) and since this table is not related to log level, it doesn't have the LOGLEVEL parameter and trying to print the LOGLEVEL for this table, end with "Unknown log level" output and due to that, errorCount is increased (as you can see here)

Steps to reproduce the issue:

  1. Run "swssloglevel -p" command
  2. The output of the command will contain "Unknown log level" for JINJA2_CACHE

Describe the results you received:

admin@r-bulldog-02:~$ swssloglevel -p JINJA2_CACHE Unknown log level SAI_API_ACL SAI_LOG_LEVEL_NOTICE SAI_API_BFD SAI_LOG_LEVEL_NOTICE SAI_API_BMTOR SAI_LOG_LEVEL_NOTICE SAI_API_BRIDGE SAI_LOG_LEVEL_NOTICE SAI_API_BUFFER SAI_LOG_LEVEL_NOTICE SAI_API_COUNTER SAI_LOG_LEVEL_NOTICE SAI_API_DEBUG_COUNTER SAI_LOG_LEVEL_NOTICE SAI_API_DTEL SAI_LOG_LEVEL_NOTICE SAI_API_FDB SAI_LOG_LEVEL_NOTICE SAI_API_HASH SAI_LOG_LEVEL_NOTICE SAI_API_HOSTIF SAI_LOG_LEVEL_NOTICE SAI_API_IPMC SAI_LOG_LEVEL_NOTICE SAI_API_IPMC_GROUP SAI_LOG_LEVEL_NOTICE SAI_API_IPSEC SAI_LOG_LEVEL_NOTICE SAI_API_ISOLATION_GROUP SAI_LOG_LEVEL_NOTICE SAI_API_L2MC SAI_LOG_LEVEL_NOTICE SAI_API_L2MC_GROUP SAI_LOG_LEVEL_NOTICE SAI_API_LAG SAI_LOG_LEVEL_NOTICE SAI_API_MACSEC SAI_LOG_LEVEL_NOTICE SAI_API_MCAST_FDB SAI_LOG_LEVEL_NOTICE SAI_API_MIRROR SAI_LOG_LEVEL_NOTICE SAI_API_MPLS SAI_LOG_LEVEL_NOTICE SAI_API_MY_MAC SAI_LOG_LEVEL_NOTICE SAI_API_NAT SAI_LOG_LEVEL_NOTICE SAI_API_NEIGHBOR SAI_LOG_LEVEL_NOTICE SAI_API_NEXT_HOP SAI_LOG_LEVEL_NOTICE SAI_API_NEXT_HOP_GROUP SAI_LOG_LEVEL_NOTICE SAI_API_POLICER SAI_LOG_LEVEL_NOTICE SAI_API_PORT SAI_LOG_LEVEL_NOTICE SAI_API_QOS_MAP SAI_LOG_LEVEL_NOTICE SAI_API_QUEUE SAI_LOG_LEVEL_NOTICE SAI_API_ROUTE SAI_LOG_LEVEL_NOTICE SAI_API_ROUTER_INTERFACE SAI_LOG_LEVEL_NOTICE SAI_API_RPF_GROUP SAI_LOG_LEVEL_NOTICE SAI_API_SAMPLEPACKET SAI_LOG_LEVEL_NOTICE SAI_API_SCHEDULER SAI_LOG_LEVEL_NOTICE SAI_API_SCHEDULER_GROUP SAI_LOG_LEVEL_NOTICE SAI_API_SRV6 SAI_LOG_LEVEL_NOTICE SAI_API_STP SAI_LOG_LEVEL_NOTICE SAI_API_SWITCH SAI_LOG_LEVEL_NOTICE SAI_API_SYSTEM_PORT SAI_LOG_LEVEL_NOTICE SAI_API_TAM SAI_LOG_LEVEL_NOTICE SAI_API_TUNNEL SAI_LOG_LEVEL_NOTICE SAI_API_UDF SAI_LOG_LEVEL_NOTICE SAI_API_VIRTUAL_ROUTER SAI_LOG_LEVEL_NOTICE SAI_API_VLAN SAI_LOG_LEVEL_NOTICE SAI_API_WRED SAI_LOG_LEVEL_NOTICE buffermgrd NOTICE coppmgrd NOTICE fdbsyncd NOTICE fpmsyncd NOTICE gearsyncd NOTICE intfmgrd NOTICE nbrmgrd NOTICE neighsyncd NOTICE orchagent NOTICE portmgrd NOTICE portsyncd NOTICE syncd NOTICE teammgrd NOTICE teamsyncd NOTICE tlm_teamd NOTICE tunnelmgrd NOTICE vlanmgrd NOTICE vrfmgrd NOTICE vxlanmgrd NOTICE

Describe the results you expected:

The same as we got but without the following line:

JINJA2_CACHE Unknown log level

Output of show version:

SONiC Software Version: SONiC.202205.150399-c9ba82777 Distribution: Debian 11.5 Kernel: 5.10.0-12-2-amd64 Build commit: c9ba82777 Build date: Mon Sep 19 17:17:43 UTC 2022 Built by: AzDevOps@sonic-build-workers-00248G

Platform: x86_64-mlnx_msn2100-r0 HwSKU: ACS-MSN2100 ASIC: mellanox ASIC Count: 1 Serial Number: MT1651X07589 Model Number: MSN2100-CB2FO Hardware Revision: A1 Uptime: 07:59:46 up 3 min, 1 user, load average: 1.78, 1.32, 0.56 Date: Wed 21 Sep 2022 07:59:46

Docker images: REPOSITORY TAG IMAGE ID SIZE docker-syncd-mlnx 202205.150399-c9ba82777 fd3e12d4f284 845MB docker-syncd-mlnx latest fd3e12d4f284 845MB docker-platform-monitor 202205.150399-c9ba82777 40a8b5e175a6 848MB docker-platform-monitor latest 40a8b5e175a6 848MB docker-orchagent 202205.150399-c9ba82777 2b9450a447a4 473MB docker-orchagent latest 2b9450a447a4 473MB docker-fpm-frr 202205.150399-c9ba82777 7bc13510648b 484MB docker-fpm-frr latest 7bc13510648b 484MB docker-teamd 202205.150399-c9ba82777 6a6dbf39ed65 455MB docker-teamd latest 6a6dbf39ed65 455MB docker-macsec latest 2c6cdc3df6d5 457MB docker-dhcp-relay latest 4184afa8f64e 448MB docker-sonic-telemetry 202205.150399-c9ba82777 04a308a064e9 519MB docker-sonic-telemetry latest 04a308a064e9 519MB docker-snmp 202205.150399-c9ba82777 1197a0ea6cfe 483MB docker-snmp latest 1197a0ea6cfe 483MB docker-router-advertiser 202205.150399-c9ba82777 b1cb5e917363 439MB docker-router-advertiser latest b1cb5e917363 439MB docker-mux 202205.150399-c9ba82777 610db86b85dd 487MB docker-mux latest 610db86b85dd 487MB docker-lldp 202205.150399-c9ba82777 371214139155 481MB docker-lldp latest 371214139155 481MB docker-database 202205.150399-c9ba82777 f1ad2d543440 439MB docker-database latest f1ad2d543440 439MB docker-nat 202205.150399-c9ba82777 d5586c9ea1b0 430MB docker-nat latest d5586c9ea1b0 430MB docker-sflow 202205.150399-c9ba82777 771e4b325678 428MB docker-sflow latest 771e4b325678 428MB docker-sonic-mgmt-framework 202205.150399-c9ba82777 d854dc018ae5 557MB docker-sonic-mgmt-framework latest d854dc018ae5 557MB

(paste your output here)

Output of show techsupport:

(paste your output here or download and attach the file here )

Additional information you deem important (e.g. issue happens only occasionally):

dprital commented 1 year ago

Suggested solution, to cherry pick the following PR to 202205: https://github.com/sonic-net/sonic-buildimage/pull/12155

gechiang commented 1 year ago

@dprital looks like you found the issue and have a PR to fix it already. Since the PR is merged, I will go ahead and close this issue.