[pre-sve] TC-SU-2.3 fail to start new CASE session with ota-provider

[pankore]

Problem

Test case ID: TC-SU-2.3
SHA: 425f1fb
Platform: Ameba all-clusters-app
Chip-tool platform: Raspberry Pi
OTA provider platform: Linux ota-provider on rpi4

• After killing the ota-provider and waiting for the update state to become idle, DUT (ota-requestor) is unable to start CASE session with OTA-provider.
• Referring to [OTA-R] TC-SU-2.3 OTA-R unable to start new CASE session with OTA-P #18642, after DUT times out, [SWU]CASE session may be invalid, tear down session. is not printed in the DUT logs

Steps to reproduce:

• Commission DUT and OTAP, start OTA transfer by announce-ota-provider command
• Kill OTA image transfer midway, wait for DUT to time out and check its update state == 1 (idle)
• Relaunch a new OTAP session, commission new OTAP
• Start OTA transfer by annouce-ota-provider command

TC-SU-2.3-chip-tool.txt
TC-SU-2.3-DUT.txt

[isiu-apple]

In TC-SU-2.3-DUT.txt, I do see: chip[SWU] CASE session may be invalid, tear down session. I also see: chip[SWU] Query already in progress.

Are you testing with this change also? #18765

[pankore]

@isiu-apple no, #18765 was not included. chip[SWU] CASE session may be invalid, tear down session. I also see: chip[SWU] Query already in progress is not printed when the initial OTA transfer time out, but is printed when it is querying the new OTA provider.

[pankore]

Closing this issue as #18765 was not merged at the time of testing. Will test again with SHA that includes the fix and reopen if issue persists. Thanks.