[CERT-TEST-FAILURE] TC-SU-2.6 - In Test step 2 BootReason value should be 5(SoftwareUpdateCompleted) After completing the Software update instead of 0(Unspecified).

[Ashwinigrl]

Feature Area

Other

Test Case

TC-SU-2.6

Reproduction steps

1. Bring up the OTA-Provider: ./chip-ota-provider-app --discriminator 3840 --KVS ~/provider/chip_kvs_provider --filepath ota-requestor-app.ota
2. Commission the OTA-Provider with chip-tool using the following command:
   ./chip-tool pairing onnetwork-long 123 20202021 3840
3. Bring up the OTA-Requestor: ./chip-ota-requestor-app --discriminator 3841 --secured-device-port 5541 --KVS ~/requestor/chip_kvs_requestor --periodicQueryTimeout 86300 --otaDownloadPath ota-requestor-app.ota --autoApplyImage --watchdogTimeout 86400
4. Commission the OTA-Requestor with chip-tool using the following command:
   ./chip-tool pairing onnetwork-long 321 20202021 3841
5. Before announcing the OTA provider, set up ACL (Access Control List) to allow OTA communication.
   ./chip-tool accesscontrol write acl '[{"fabricIndex": 1, "privilege": 5, "authMode": 2, "subjects": [112233], "targets": null}, {"fabricIndex": 1, "privilege": 3, "authMode": 2, "subjects": [321], "targets": null}]' 123 0
6. Send the OTA Provider announces to the OTA Requestor:
   ./chip-tool otasoftwareupdaterequestor announce-otaprovider 123 0 0 0 321 0
7. Once the DUT(OTA-Requestor) sends the NotifyUpdateApplied Command to the OTA-P after installing the software update. Then Verify that the NotifyUpdateApplied message received on the OTA-P has the following fields.

• UpdateToken - verify that it is the same as the one provided by the OTA provider in the QueryImageResponse.
• SoftwareVersion - verify the software version on the DUT to match the version downloaded for the software update.

[1741162881.019] [82638:82638] [DMG] Received command for Endpoint=0 Cluster=0x0000_0029 Command=0x0000_0004
[1741162881.019] [82638:82638] [ZCL] OTA Provider received NotifyUpdateApplied
[1741162881.019] [82638:82638] [ZCL] Update Token: 32
[1741162881.019] [82638:82638] [ZCL] Software Version: 2

Here UpdateToken is same as the one provided by the OTA provider in the QueryImageResponse.

[1741089252.355] [68660:68660] [DMG] Received Command Response Data, Endpoint=0 Cluster=0x0000_0029 Command=0x0000_0001
[1741089252.355] [68660:68660] [SWU] QueryImageResponse:
[1741089252.355] [68660:68660] [SWU] status: 0
[1741089252.355] [68660:68660] [SWU] imageURI: bdx://000000000000007B/ota-requestor-app.ota
[1741089252.355] [68660:68660] [SWU] softwareVersion: 2
[1741089252.355] [68660:68660] [SWU] softwareVersionString: 2.0
[1741089252.355] [68660:68660] [SWU] updateToken: 32
[1741089252.355] [68660:68660] [SWU] userConsentNeeded: 0
[1741089252.355] [68660:68660] [SWU] Update available from version 1 to 2

software version on the DUT has been updated from 1 to 2.

./chip-tool basicinformation read software-version 321 0

[1741169218.145] [94180:94182] [TOO] Endpoint: 0 Cluster: 0x0000_0028 Attribute 0x0000_0009 DataVersion: 1172353301
[1741169218.145] [94180:94182] [TOO] SoftwareVersion: 2

8. TH reads BootReason in General Diagnostics cluster from the DUT. Verify that the returned value of BootReason is SoftwareUpdateCompleted(5)

./chip-tool generaldiagnostics read boot-reason 321 0

Actual Outcome:

[1741169351.923] [94188:94190] [TOO] Endpoint: 0 Cluster: 0x0000_0033 Attribute 0x0000_0004 DataVersion: 3930602256
[1741169351.923] [94188:94190] [TOO] BootReason: 0

Expected Outcome:

[1741169351.923] [94188:94190] [TOO] Endpoint: 0 Cluster: 0x0000_0033 Attribute 0x0000_0004 DataVersion: 3930602256
[1741169351.923] [94188:94190] [TOO] BootReason: 5

Bug prevalence

Whenever I do this

GitHub hash of the SDK that was being used

13da787

Platform

raspi

Anything else?

TC-SU-2.6 - In Test step 2 is expecting to read BootReason value in General Diagnostics cluster from the DUT once the DUT sends the NotifyUpdateApplied Command to the OTA-P after installing the software update. But When we try to read the BootReason value from the DUT after installing the software update from the OTA provider, Getting value as 0(Unspecified) instead of 5(SoftwareUpdateCompleted). Hence Sample app(OTA Requestor app has to be updated accordingly.

Test plan References:

• https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/softwareupdate.adoc#test-procedure-6

Specification References:

• https://github.com/CHIP-Specifications/connectedhomeip-spec/blob/master/src/service_device_management/OTASoftwareUpdate.adoc#36-applying-a-software-update

Reference logs:

TC-SU-2.6.txt