Open gechiang opened 3 years ago
Confirmed that the change from [debugcounterorch] check if counter type is supported before querying… ( 04105a4 is exposing the BRCM SAI issue where the count check was failing.
void DebugCounterOrch::publishDropCounterCapabilities()
{
supported_ingress_drop_reasons = DropCounter::getSupportedDropReasons(SAI_DEBUG_COUNTER_ATTR_IN_DROP_REASON_LIST);
supported_egress_drop_reasons = DropCounter::getSupportedDropReasons(SAI_DEBUG_COUNTER_ATTR_OUT_DROP_REASON_LIST);
supported_counter_types = DropCounter::getSupportedCounterTypes();
string ingress_drop_reason_str = DropCounter::serializeSupportedDropReasons(supported_ingress_drop_reasons);
string egress_drop_reason_str = DropCounter::serializeSupportedDropReasons(supported_egress_drop_reasons);
for (auto const &counter_type : DebugCounter::getDebugCounterTypeLookup())
{
string drop_reasons;
if (!supported_counter_types.count(counter_type.first)) <== This check is causing StateDB not having the CAPABILITY for BRCM platforms
{
continue;
}
...
BRCM case CS00012205138 filed
Revert commit on 202012 branch - https://github.com/Azure/sonic-swss/pull/1884. Issue is still present on master
Discussed with BRCM and Genhwa will take a look.
Description
DropCounter configuration on all BRCM platform stopped working after the 07/31/21 202012 build.
Steps to reproduce the issue:
This is all because STATE DB is missing the DEBUG_COUNTER_CAPABILITIES for BRCM platforms.
Describe the results you expected:
On a working image (202012 image built on 07/30/21 or earlier), you see the following:
Output of
show version
:Here are the changes that went into the build of 07/31/21:
Additional information you deem important (e.g. issue happens only occasionally):