Merged
Conversation
…tack (#220) Reason for change: Default file should be fetched based on Devicemode for Onestack products. Test Procedure: Set Devicemode to residential/business, and ensure proper system_default file is loaded. Risks: medium Priority: P1
…ice Interface creation (#171) **Reason for change**:Setting the default variables for virtual voice interface creation **Test Procedure**: verify the virtual voice interface creation functionality. **Risks**: High **Priority**: P1
Release 2.2.0 2.2.0
RDKB-60656 : Available memory check for firmware downloads Reason for change: Before firmware download, we need to check if the device have enough memory Test Procedure: 1. while firmware download, available memory check logs should be seen. 2. If available memory < required memory, firmware download should not start. Risks: medium Priority: P1 Dependent PRs: rdkcentral/xconf-client#13 rdkcentral/provisioning-and-management#178 #182 rdkcentral/cable-modem-agent#23 rdkcentral/miscellaneous-broadband#37 https://github.com/rdk-gdcs/apparmor-profiles/pull/49 Dependent Gerrits: https://gerrit.teamccp.com/#/q/topic:RDKB-60656+(status:open+OR+status:merged)
#222) RDKB-63137 RDKB-63542: Ability to Toggle DeviceMode Using ActivatePartnerID Support Reason for Change: RDKB‑63470 is a sub‑task under the RDKB‑63137 user story to implement support for the TR‑181 DeviceMode parameter. This update ensures correct toggling of DeviceMode through ActivatePartnerID. Test Procedure: The build should compile successfully, and TR‑181 operations—including setting PartnerID and activating PartnerID—must function without errors. DeviceMode transitions (residential ↔ business) should be validated as per the test steps. Risks: Low. Signed-off-by: [Goutam_Damodaran@comcast.com](mailto:Goutam_Damodaran@comcast.com)
…tarting the zebra in XLE (#181) **LTE-2775 :** Observing RDKB_PROCESS_CRASHED : zebra is not running, restarting the zebra in XLE Reason for change: 1. The zebra restart logic requires **bridge mode to be 0 and the LAN to be fully started**. Previously, both LAN startup and the zebra start were triggered from the same location in service_devicemode.c. In cases where LAN initialization was slightly delayed, zebra startup would fail because it was being triggered before the LAN was ready. 2. To address this, zebra startup has been moved to service_routed.sh, ensuring that the zebra process is started only after the LAN is fully initialized. Test Procedure: Check zebra process when XLE is in router mode. Risks: Low Priority: P1 --------- Signed-off-by: aj970 <akshaya_j@comcast.com> Co-authored-by: Santosh Nayak <70348540+snayak002c@users.noreply.github.com>
Reason for change: Receive the MAP-E options from DhcpManager and configure the tunnel interface. Test Procedure: Verify functionality by passing DHCPv6 Option 94 and the ip6tnl tunnel interface is correctly configured and brought up. Testing Done : Results are captured in RDKBNETWOR-77 --------- Signed-off-by: Krithiksha Prabhakar <krithiksha.prabhakar@telekom-digital.com> Co-authored-by: Parthiban Selvaraj <167313466+S-Parthiban-Selvaraj@users.noreply.github.com> Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
RDKB-63584 : dibbler-server is not running when enable the DHCPMANAGER Reason for change: pmon is disabled in dhcpmanager enabled build, this was disabled for older DHCPMANAGER for Xb6 platform Test Procedure: kill dnsmasq and dibbler-server , check selfheal restarts it Risks: Low Signed-off-by:Aadhithan_PE@comcast.com UT:https://ccp.sys.comcast.net/browse/RDKB-63584?focusedId=24660985&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-24660985
Rdkb 63584: srv_unregister remove DHCPManager Distro This PR removes the DHCP Manager distro-specific compile guard in the DHCP server registration helper so that srv_unregister() always unregisters dhcp_server from pmon, aligning unregister behavior with the existing unconditional srv_register() behavior. Changes: Remove the #if !defined(FEATURE_RDKB_DHCP_MANAGER) guard around pmon.sh unregister dhcp_server. Drop the associated comment about the DHCP Manager self-heal mechanism.
US: RDKB-62968: Subtask: RDKB-63632 - Addition of RFC parameter for Stage Agent Reason for change: Add RFC flag Device.DeviceInfo.X_RDKCENTRAL-COM_RFC.Feature.STAGE.Enable to execute the app Test Procedure: Build with stage agent changes and test Risks: None Is this a Bug or a User Story (US)?: US: RDKB-62968 - STAGE development - Phase 1 (SSH trigger). Subtask: RDKB-63632 2. If it is a User Story: * Have all dependent PRs from other components been listed (if any)?: Below PR's are dependent PR's rdkcentral/tr69hostif#366 #235 rdkcentral/provisioning-and-management#195 * Does the commit message include both the User Story ticket and the Subtask ticket? Yes * Will be all changes related to the User Story squashed and merged in a single commit?: No * Has the PR been raised only after completing all changes for the User Story (no partial changes)? : Yes * Has code development for the User Story been completed?: Yes * If yes, has the Gerrit topic or list of all dependent PRs across components (including meta-layer changes) been shared?:topic: https://gerrit.teamccp.com/#/q/topic:RDKB-62968-StageAgent-26Q1_sprint+(status:open+OR+status:merged) 3. Is there a validation log available in the Jira ticket for verifying builds with the updated generic-srcrev.inc across all platforms?: Yes * If yes, have the links to validation comments been shared?: https://ccp.sys.comcast.net/secure/attachment/14230070/14230070_D89C8E72F2E0_Stage_Logs_02-20-26-06-19AM.tgz Signed-off-by: rriyaz502 <Riyaz_Riyaz@comcast.com> Co-authored-by: rriyaz502 <Riyaz_Riyaz@comcast.com>
|
I have read the CLA Document and I hereby sign the CLA 7 out of 8 committers have signed the CLA. |
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.
10 participants
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.
No description provided.