Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TC-MF-1.4] DUT abort in SendReportData function when Second Controller Commissions and read attribute #10662

Closed
praveenCY opened this issue Oct 19, 2021 · 10 comments
Assignees
Milestone

Comments

@praveenCY
Copy link
Contributor

Problem

DUT aborts in SendReportData function when Second Controller completes commissioning and read attribute like FabricsList.

Steps:
[TC-MF-1.4] Node Behavior using BCM [DUT - Commissionee]

  1. TH_CR1 starts a commissioning process with DUT_CE

  2. If (PICS_MF_BCM) TH_CR1 opens a commissioning window on DUT_CE using a commissioning timeout of PIXIT_COMM_WIN seconds using BCM
    zcl AdministratorCommissioning OpenBasicCommissioningWindow 12344321 0 0 commissioningTimeout=500

  3. TH_CR1 writes and reads the Basic Information Cluster’s NodeLabel mandatory attribute of DUT_CE
    zclwrite Basic UserLabel 12344321 0 0 TE5New
    zclread Basic UserLabel 12344321 0 0

  4. TH_CR2 starts a commissioning process with DUT_CE
    connect -ip 192.168.1.111 20202021 12345678

  5. TH_CR1 reads the list of Fabrics on DUT_CE
    zclread OperationalCredentials FabricsList 12344321 0 0

  6. TH_CR2 reads the list of Fabrics on DUT_CE
    zclread OperationalCredentials FabricsList 12345678 0 0 ==> This fails and DUT abort happens

Logs : DUT_abort_log.txt

image

Proposed Solution

@mrjerryjohns
Copy link
Contributor

Can you please provide full logs from both the DUT and and the controller?

@praveenCY
Copy link
Contributor Author

Can you please provide full logs from both the DUT and and the controller?
is this not enough ? https://github.com/project-chip/connectedhomeip/files/7375918/DUT_abort_log.txt

@praveenCY
Copy link
Contributor Author

praveenCY commented Oct 21, 2021

Detailed log from Controller: LOCK-TC-MF-1.4.txt

@yunhanw-google
Copy link
Contributor

I try this in master branch, and cannot reproduce this issue, what is the commit you are using?

@praveenCY
Copy link
Contributor Author

I try this in master branch, and cannot reproduce this issue, what is the commit you are using?
Running on test_event_6 branch for TE6

commit 82bcd4e (HEAD -> test_event_6, origin/test_event_6)
Author: Damian Królik [email protected]
Date: Thu Sep 30 03:23:48 2021 +0200
[clusters] Fix scheduled actions in clusters (#10001)

One thing I noticed is that during this issue "new session is created during Fabricslist read" in Controller Side

[1634855905.718853][3320:3328] CHIP:IN: New secure session created for device 0x0000000000000385, key 4!!

@yunhanw-google
Copy link
Contributor

I also cannot reproduce this in TE6 branch, any build option during compilation have you used?

@yunhanw-google
Copy link
Contributor

TH_CR1 and TH_CR2 are residing in two different machine node? I am using two different node for testing.

@praveenCY
Copy link
Contributor Author

Setup details
Two Raspberry Pi4 with TE6 image from https://drive.google.com/file/d/1HWF8JAQ8HEPTi-Hx3Ds9CFiPTUCYvX6x

  • First pi4 Commission with chip-device-ctrl -n 9999 (chip-device-ctrl is pre-built and available with this Pi4)
    ubuntu@matter-te-6:~$ which chip-device-ctrl
    /home/ubuntu/.local/bin/chip-device-ctrl

  • Second Pi4 with chip-device-ctrl -n 8888 (same location as above)

@praveenCY
Copy link
Contributor Author

Tried the same TC with master branch

commit edc22bd (HEAD -> master, origin/master, origin/HEAD)
Author: Vivien Nicolas [email protected]
Date: Wed Oct 27 22:02:31 2021 +0200

Logs: LOCK-TC-MF-1.4-MasterFailureLog.txt

@praveenCY
Copy link
Contributor Author

Closing this as this is not seen with master branch and open #11092 for the issue seen with master branch

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

4 participants