connectedhomeip: [BUG] Error on TC-DRLK-2.8 execution (CONSTRAINT_ERROR)

Reproduction steps

1. Run chip-all-clusters-app
2. Use chip-tool to execute the test steps for TC-DRLK-2.8:

Commission DUT:

./chip-tool pairing code 1 MT:-24J0AFN00KA0648G00

Step 1:

./chip-tool doorlock read number-of-total-users-supported 1 1

Step 2:

./chip-tool doorlock set-user 0 1 xxx 6452 1 0 0 1 1  --timedInteractionTimeoutMs 1000

Step 3:

./chip-tool doorlock get-user 1 1 1

Step 4:

./chip-tool doorlock set-user 0 2 xxx 6451 1 10 3 1 1 --timedInteractionTimeoutMs 1000

Step 5:

./chip-tool doorlock set-user 0 1 xxx 8965 1 0 0 1 1 --timedInteractionTimeoutMs 1000

Step 6a:

./chip-tool doorlock set-user 0 2 null null null null null 1 1 --timedInteractionTimeoutMs 1000

Step 6b:

./chip-tool doorlock get-user 2 1 1

Step 7:

./chip-tool doorlock set-user 2 2 null null null null null 1 1 --timedInteractionTimeoutMs 1000

Step 8:

./chip-tool doorlock get-user 2 1 1

Step 9:

./chip-tool doorlock clear-user 1 1 1  --timedInteractionTimeoutMs 1000

Step 10:

./chip-tool doorlock get-user 1 1 1  --timedInteractionTimeoutMs 1000

Decommission DUT:

./chip-tool pairing unpair 1

Error

On step 4, the expected response is:

[1657607954.930591][7988:7993] CHIP:DMG: {
[1657607954.930618][7988:7993] CHIP:DMG:        suppressResponse = false,
[1657607954.930651][7988:7993] CHIP:DMG:        InvokeResponseIBs =
[1657607954.930688][7988:7993] CHIP:DMG:        [
[1657607954.930716][7988:7993] CHIP:DMG:                InvokeResponseIB =
[1657607954.930755][7988:7993] CHIP:DMG:                {
[1657607954.930787][7988:7993] CHIP:DMG:                        CommandStatusIB =
[1657607954.930825][7988:7993] CHIP:DMG:                        {
[1657607954.930862][7988:7993] CHIP:DMG:                                CommandPathIB =
[1657607954.930900][7988:7993] CHIP:DMG:                                {
[1657607954.930942][7988:7993] CHIP:DMG:                                        EndpointId = 0x1,
[1657607954.930984][7988:7993] CHIP:DMG:                                        ClusterId = 0x101,
[1657607954.931027][7988:7993] CHIP:DMG:                                        CommandId = 0x1a,
[1657607954.931065][7988:7993] CHIP:DMG:                                },
[1657607954.931107][7988:7993] CHIP:DMG:
[1657607954.931142][7988:7993] CHIP:DMG:                                StatusIB =
[1657607954.931180][7988:7993] CHIP:DMG:                                {
[1657607954.931218][7988:7993] CHIP:DMG:                                        status = 0x85 (INVALID_COMMAND),
[1657607954.931259][7988:7993] CHIP:DMG:                                },
[1657607954.931296][7988:7993] CHIP:DMG:
[1657607954.931333][7988:7993] CHIP:DMG:                        },
[1657607954.931371][7988:7993] CHIP:DMG:
[1657607954.931402][7988:7993] CHIP:DMG:                },
[1657607954.931439][7988:7993] CHIP:DMG:
[1657607954.931466][7988:7993] CHIP:DMG:        ],
[1657607954.931500][7988:7993] CHIP:DMG:
[1657607954.931527][7988:7993] CHIP:DMG:        InteractionModelRevision = 1
[1657607954.931553][7988:7993] CHIP:DMG: },
[1657607954.931617][7988:7993] CHIP:DMG: Received Command Response Status for Endpoint=1 Cluster=0x0000_0101 Command=0x0000_001A Status=0x85
[1657607954.931654][7988:7993] CHIP:TOO: Error: IM Error 0x00000585: General error: 0x85 (INVALID_COMMAND)

Instead, chip-tool is giving the error: CHIP:TOO: Run command failure: src/app/data-model/Encode.h:75: IM Error 0x00000587: General error: 0x87 (CONSTRAINT_ERROR)

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

9ac148067fb9c5a4aadab1fdecd0a8b4e22e6da0

Platform

other

Platform Version(s)

No response

Anything else?

Logs

• chip-all-clusters-app logs: chip-all-clusters-app.log
• chip-tool logs: chip-tool.log

Test plan verification steps

• The test case steps and expected results were taken from: https://groups.csa-iot.org/wg/matter-csg/document/28567

Additional testing

I also tested the same test case using chip-lock-app, but go the same result:

• chip-lock-app logs: 2_chip-lock-app.log
• chip-tool logs: 2_chip-tool.log

Additional Comments

This bug has been found when trying to run TC-DRLK-2.6 and TC-DRLK-2.8 in Test Harness. This same error is also happening when running TC-DRLK-2.6. I believe the root cause is probably be the same.

• Logs from Test Harness running both TC-DRLK-2.6 and TC-DRLK-2.8: UI_Test_Run_2023_07_14_16_03_37.log

Test Harness related issues

• TC-DRLK-2.8 issue: https://github.com/CHIP-Specifications/chip-certification-tool/issues/897
• TC-DRLK-2.6 issue: https://github.com/CHIP-Specifications/chip-certification-tool/issues/895