[Test Script] TC-GRPKEY-2.2: Test case fails because the expected EXHAUSTED error is not detected by Test Harness

Description:

During manual execution of the affected test scenario using chip-tool, the procedure results in an EXHAUSTED error. This EXHAUSTED error is the expected outcome for this test scenario.

However, when the same scenario is executed using the CSA Test Harness, the Test Harness does not detect/recognize the EXHAUSTED error.

As a result, the Test Harness evaluates the test step incorrectly and the test case fails, even though the DUT behavior matches the expected behavior and the expected EXHAUSTED error is observed during manual execution.

I noticed that the same issue was reported earlier in this https://github.com/project-chip/matter-test-scripts/issues/275

but the solution given in that also did not work for me.

Logs:

The chip-tool execution shows the expected EXHAUSTED error.

TC-GRPKEY-2_2.log

Test Harness execution:

TC-GRPKEY-2_2_2026_08_13_13_16_56.log

Start by comparing the TC-GRPKEY-2.2 chip-tool log with the CSA Test Harness log and review the earlier issue #275. Trace where the test case evaluates the EXHAUSTED result and reproduce the failure. Done means the harness recognizes the expected EXHAUSTED error and the test case passes.