[CERT-TEST-FAILURE]-TC-CNET- 4.11 - Test failed

[Survensa]

Feature Area

Other

Test Case

TC-CNET-4.11

Summary

TH should be able to connect DUT using 1st ACCESSPOINT with connected status as TRUE when the fail-safe is disarmed after connecting to 2nd ACCESSPOINT.

Reproduction steps

1. Paired TH ( CHIP_TOOL ) and DUT ( ALL-CLUSTERS-APP) through ble-wifi

2. Armed the fail-safe : ./chip-tool generalcommissioning arm-fail-safe 900 1 1 0

3. Checked the 1st connected ACCESSPOINT : ./chip-tool networkcommissioning read networks 1 0

[1657733068.835240][7475:7480] CHIP:TOO:   Networks: 1 entries
[1657733068.835354][7475:7480] CHIP:TOO:     [1]: {
[1657733068.835434][7475:7480] CHIP:TOO:       NetworkID: 47524C50726976617465
[1657733068.835487][7475:7480] CHIP:TOO:       Connected: TRUE
[1657733068.835535][7475:7480] CHIP:TOO:      }

5. Removed the network :
   ./chip-tool networkcommissioning remove-network hex:47524C50726976617465 1 0 --Breadcrumb 1

6. Added 2nd ACCESSPOINT network : ./chip-tool networkcommissioning add-or-update-wi-fi-network Sbee_Moto Sunsuraj 1 0 --Breadcrumb 1

7. Connected 2nd network and checked the network status : ./chip-tool networkcommissioning connect-network hex:536265655F4D6F746F 1 0 --Breadcrumb 2 and ./chip-tool networkcommissioning read networks 1 0

[1657733596.457792][7640:7645] CHIP:TOO:   Networks: 1 entries
[1657733596.457867][7640:7645] CHIP:TOO:     [1]: {
[1657733596.457906][7640:7645] CHIP:TOO:       NetworkID: 536265655F4D6F746F
[1657733596.457940][7640:7645] CHIP:TOO:       Connected: TRUE
[1657733596.457972][7640:7645] CHIP:TOO:      }

10. Now Disarmed the fail-safe : ./chip-tool generalcommissioning arm-fail-safe 0 0 1 0

11. Checked whether the network is reverted to 1st ACCESS POINT : ./chip-tool networkcommissioning read networks 1 0

Actual Outcome :

[1684497703.596592][3941:3943] CHIP:TOO:   Networks: 1 entries
[1684497703.596640][3941:3943] CHIP:TOO:     [1]: {
[1684497703.596668][3941:3943] CHIP:TOO:       NetworkID: 47524C50726976617465
[1684497703.596697][3941:3943] CHIP:TOO:       Connected: FALSE
[1684497703.596721][3941:3943] CHIP:TOO:      }

Expected Outcome:

[1684497703.596592][3941:3943] CHIP:TOO:   Networks: 1 entries
[1684497703.596640][3941:3943] CHIP:TOO:     [1]: {
[1684497703.596668][3941:3943] CHIP:TOO:       NetworkID: 47524C50726976617465
[1684497703.596697][3941:3943] CHIP:TOO:       Connected: TRUE
[1684497703.596721][3941:3943] CHIP:TOO:      }

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

bfa05804ac3c224c9e70921a857ffcac32ccc7f4

Platform

raspi

Platform Version(s)

RPI-4, 8GB-RAM variant

Log :

• TC_CNET_4_11_CNTRL.txt

• TC_CNET_4_11_DUT.txt

[andy31415]

This may not make it to Sep1 due to seemingly more complex changes. It is odd that the network list says "not connected" yet we are communicating via chip-tool (presumably over ip).

[cecille]

which network is the TH connected to when it sends the ./chip-tool networkcommissioning read networks 1 0 command?

The steps here don't match up with the test plan - is the TH swapping its own network?