4dc61fcbc1
- Why I did it Fixes #14236 When a redis event quickly gets outdated during port breakout, error logs like this are seen Mar 8 01:43:26.011724 r-leopard-56 INFO ConfigMgmt: Write in DB: {'PORT': {'Ethernet64': {'admin_status': 'down'}, 'Ethernet68': {'admin_status': 'down'}}} Mar 8 01:43:26.012565 r-leopard-56 INFO ConfigMgmt: Writing in Config DB Mar 8 01:43:26.013468 r-leopard-56 INFO ConfigMgmt: Write in DB: {'PORT': {'Ethernet64': None, 'Ethernet68': None}, 'INTERFACE': None} Mar 8 01:43:26.018095 r-leopard-56 NOTICE swss#portmgrd: :- doTask: Configure Ethernet64 admin status to down Mar 8 01:43:26.018309 r-leopard-56 NOTICE swss#portmgrd: :- doTask: Delete Port: Ethernet64 Mar 8 01:43:26.018641 r-leopard-56 NOTICE lldp#lldpmgrd[32]: :- pops: Miss table key PORT_TABLE:Ethernet64, possibly outdated Mar 8 01:43:26.018654 r-leopard-56 ERR lldp#lldpmgrd[32]: unknown operation '' - How I did it Only log the error when the op is not empty and not one of ("SET" & "DEL" ) Signed-off-by: Vivek Reddy Karri <vkarri@nvidia.com> |
||
|---|---|---|
| .. | ||
| docker-base | ||
| docker-base-bullseye | ||
| docker-base-buster | ||
| docker-base-stretch | ||
| docker-basic_router | ||
| docker-config-engine | ||
| docker-config-engine-bullseye | ||
| docker-config-engine-buster | ||
| docker-config-engine-stretch | ||
| docker-database | ||
| docker-dhcp-relay | ||
| docker-eventd | ||
| docker-fpm-frr | ||
| docker-fpm-gobgp | ||
| docker-iccpd | ||
| docker-lldp | ||
| docker-macsec | ||
| docker-mux | ||
| docker-nat | ||
| docker-orchagent | ||
| docker-pde | ||
| docker-platform-monitor | ||
| docker-ptf | ||
| docker-ptf-sai | ||
| docker-router-advertiser | ||
| docker-sflow | ||
| docker-snmp | ||
| docker-sonic-mgmt | ||
| docker-sonic-mgmt-framework | ||
| docker-sonic-p4rt | ||
| docker-sonic-restapi | ||
| docker-sonic-sdk | ||
| docker-sonic-sdk-buildenv | ||
| docker-sonic-telemetry | ||
| docker-swss-layer-bullseye | ||
| docker-swss-layer-buster | ||
| docker-teamd | ||
| dockerfile-macros.j2 | ||