Getting UnKnownError as status for Connect Network command.

[Saravana-kr22]

Description
When executing the script TC_Android_pair.py as a part of stress testing, in the Pase session when sending connect network command we got the respose with status = 12 (UnKnowError) with error value = -3 as below. This script will mimic on a high level how the pairing occurs in the Android ecosystem.

2025-01-17 20:38:04,793 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - InvokeResponseMessage =
2025-01-17 20:38:04,794 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - {
2025-01-17 20:38:04,794 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - suppressResponse = false,
2025-01-17 20:38:04,795 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - InvokeResponseIBs =
2025-01-17 20:38:04,795 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - [
2025-01-17 20:38:04,796 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - InvokeResponseIB =
2025-01-17 20:38:04,796 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - {
2025-01-17 20:38:04,796 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - CommandDataIB =
2025-01-17 20:38:04,797 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - {
2025-01-17 20:38:04,797 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - CommandPathIB =
2025-01-17 20:38:04,797 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - {
2025-01-17 20:38:04,797 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - EndpointId = 0x0,
2025-01-17 20:38:04,797 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - ClusterId = 0x31,
2025-01-17 20:38:04,797 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - CommandId = 0x7,
2025-01-17 20:38:04,798 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - },
2025-01-17 20:38:04,798 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 -
2025-01-17 20:38:04,798 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - CommandFields =
2025-01-17 20:38:04,798 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - {
2025-01-17 20:38:04,798 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - 0x0 = 12 (unsigned),
2025-01-17 20:38:04,798 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - 0x2 = -3 (signed),
2025-01-17 20:38:04,798 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - },
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - },
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 -
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - },
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 -
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - ],
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 -
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - InteractionModelRevision = 11
2025-01-17 20:38:04,799 - chip.native.DMG - DEBUG - init.py:_RedirectToPythonLogging:43 - },

GitHub hash of the SDK that were being used are : d96f2b5

Platforms
I Have performed the execution on Raspberrypi as DUT using ble-wifi provisioning
Test Bed :
Controller Platform - python controller running on Mac Laptop,
Raspberrypi as DUT - all-cluster-app running on Raspberrypi 4B -8GB
Provisioning method - Ble-Wifi

Test scenario
Pair/Provision the DUT (All-cluster-app running on raspi) as per drawiin pairing flow using Ble-Wifi.
Read device information after the device is provisioned
sleep for 2 secs
Unpair the DUT (i.e. removing the fabric)
Factory reset the DUT
repeat step1 - 6 for 500 iterations
Script reference: https://github.com/CHIP-Specifications/matter-qa/blob/main/src/matter_qa/scripts/reliability_scripts/TC_Android_Pair.py

Execution Details

In this Test bed for Iteration [ 146, 211, 225, 258, 295, 342, 415, 422, 433, 480, 485] has the UnKnowError status for the connect network command
Iterations scheduled to run: 500
Iterations Failed: 15
Iterations Passed: 485
Execution Logs (logs consists of 2 Pass iterations and 11 Fail Iterations):

145_passed.zip
146_Failed.zip
147_passed.zip
211_failed.zip
225_failed.zip
258_Failed.zip
295_failed.zip
342_failed.zip
415_failed.zip
422_failed.zip
433_failed.zip
480_failed.zip
485_failed.zip