Skip to content

RDKB-61372: Handling recovery cases of Unknown/Invalid syscfg PartnerID#51

Merged
anoopchelakkode merged 2 commits intordkcentral:developfrom
bytegowda:topic_RDKB_61372
Sep 16, 2025
Merged

RDKB-61372: Handling recovery cases of Unknown/Invalid syscfg PartnerID#51
anoopchelakkode merged 2 commits intordkcentral:developfrom
bytegowda:topic_RDKB_61372

Conversation

@bytegowda
Copy link

Reason for change: Add retry mechanism for PartnerID Unknown

Test Procedure:

  1. Set PartnerID via TR181 DMs
    a. Set the DM Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.PartnerId with one of following values : "Unknown", "known", "sky-", ""
    b. Set the DM dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.RDKB_Control.ActivatePartnerId bool true
    c. CPE goes for reboot and after reboot, Check if the PartnerID recovers with respective PartnerID configurations applied
    d. After Recovery Reboot Reason should be Reboot-DueTo-InvalidPartnerID

  2. Set PartnerID DB param via syscfg
    a. set PartnerID with following values : "Unknown", "known", "sky-", ""
    b. syscfg commit
    c. Reboot CPE and Check if the PartnerID recovers with respective PartnerID configurations applied
    d. After Recovery Reboot Reason should be Reboot-DueTo-InvalidPartnerID

  3. Upgrade scenario
    a. Flash image without the fix, check Partner ID - sky-uk
    b. Set Partner ID to "Unknown" using Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.PartnerId
    c. Activate PartnerID using Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.RDKB_Control.ActivatePartnerId
    d. CPE goes for reboot and after reboot, check the DMs if the partner_defaults.json loaded for Unknown in the image without the fix.
    e. Flash the image with the fix and check if the partner ID is recovered and valid config is loaded
    f. After Recovery Reboot Reason should be Reboot-DueTo-InvalidPartnerID

  4. Retry failure: If recovery fails after retry mechanism, then the PartnerID must be set to Unknown

Priority: P1

Risks: Low

Signed-off-by: Yashwanth Kumar H M yashwanthkumar.hm@sky.uk

Reason for change: Add retry mechanism for PartnerID Unknown

Test Procedure:
1. Set PartnerID via TR181 DMs
   a. Set the DM Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.PartnerId with one of following values : "Unknown", "known", "sky-", ""
   b. Set the DM dmcli eRT setv Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.RDKB_Control.ActivatePartnerId bool true
   c. CPE goes for reboot and after reboot, Check if the PartnerID recovers with respective PartnerID configurations applied
   d. After Recovery Reboot Reason should be Reboot-DueTo-InvalidPartnerID

2. Set PartnerID DB param via syscfg
   a. set PartnerID with following values :  "Unknown", "known", "sky-", ""
   b. syscfg commit
   c. Reboot CPE and Check if the PartnerID recovers with respective PartnerID configurations applied
   d. After Recovery Reboot Reason should be Reboot-DueTo-InvalidPartnerID

3. Upgrade scenario
   a. Flash image without the fix, check Partner ID - sky-uk
   b. Set Partner ID to "Unknown" using Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.PartnerId
   c. Activate PartnerID using Device.DeviceInfo.X_RDKCENTRAL-COM_Syndication.RDKB_Control.ActivatePartnerId
   d. CPE goes for reboot and after reboot, check the DMs if the partner_defaults.json loaded for Unknown in the image without the fix.
   e. Flash the image with the fix and check if the partner ID is recovered and valid config is loaded
   f. After Recovery Reboot Reason should be Reboot-DueTo-InvalidPartnerID

4. Retry failure:
   If recovery fails after retry mechanism, then the PartnerID must be set to Unknown

Priority: P1

Risks: Low

Signed-off-by: Yashwanth Kumar H M <yashwanthkumar.hm@sky.uk>
@bytegowda bytegowda requested a review from a team as a code owner September 9, 2025 16:37
@CLAassistant
Copy link

CLAassistant commented Sep 9, 2025

CLA assistant check
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ LakshminarayananShenbagaraj
❌ yashwanthkumar-hm_comcast


yashwanthkumar-hm_comcast seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
You have signed the CLA already but the status is still pending? Let us recheck it.

@anoopchelakkode anoopchelakkode merged commit ce7f6b7 into rdkcentral:develop Sep 16, 2025
4 of 6 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Sep 16, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants