RDKB-61372: Handling recovery cases of Unknown/Invalid syscfg PartnerID#51
Merged
anoopchelakkode merged 2 commits intordkcentral:developfrom Sep 16, 2025
Merged
Conversation
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>
|
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. |
snayak002c
approved these changes
Sep 16, 2025
anoopchelakkode
approved these changes
Sep 16, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Reason for change: Add retry mechanism for PartnerID Unknown
Test Procedure:
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
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
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
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