Skip to content

RDKB-60325 : notify_tunnel_status failure in hotspot#5

Open
supriya-shree1 wants to merge 21 commits intodevelopfrom
feature/update_rbus_send_data
Open

RDKB-60325 : notify_tunnel_status failure in hotspot#5
supriya-shree1 wants to merge 21 commits intodevelopfrom
feature/update_rbus_send_data

Conversation

@supriya-shree1
Copy link
Contributor

@supriya-shree1 supriya-shree1 commented Aug 12, 2025

Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified successfully
Risks: Low
Priority: P2

@supriya-shree1 supriya-shree1 requested a review from a team as a code owner August 12, 2025 08:59
@supriya-shree1 supriya-shree1 force-pushed the feature/update_rbus_send_data branch from 5d75f45 to 688a372 Compare August 14, 2025 05:25
@GoutamD2905
Copy link
Contributor

Please write the L1 Unit Test cases for the New API and resolve the existing L1 test cases failures

@sowmiyachelliah sowmiyachelliah requested review from a team as code owners November 3, 2025 17:02
@supriya-shree1
Copy link
Contributor Author

supriya-shree1 commented Dec 5, 2025

Bug Fix: TunnelStatus was not getting notified because the deprecated API CcspBaseIf_SendSignal_WithData was being used.
Change: Replaced it with rbusEvent_Publish in notify_tunnel_status to publish TunnelStatus via RBUS.
As part of this change:

  • Removed TunnelStatus parameter handling from PAM.
  • Registered TunnelStatus as an RBUS property/event in the Hotspot component.

Dependent PR: Provisioning and Management #149
[https://github.com/rdkcentral/provisioning-and-management/pull/149]
Validation: GTest results and validation logs are attached in Jira Ticket RDKB-60325.
[https://ccp.sys.comcast.net/browse/RDKB-60325]

CC: @snayak002c

supriya-shree1 and others added 20 commits December 12, 2025 04:23
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified
Risks: Low
Priority: P2
Signed-off-by:SupriyaShree_SS@comcast.com
@supriya-shree1 supriya-shree1 force-pushed the feature/update_rbus_send_data branch from e16e3ae to d70236f Compare December 12, 2025 10:58
}
};

extern char TunnelStatus[128];
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

TunnelStatus should be 8

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated

Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified successfully
Risks: Low
Priority: P2
@@ -2046,17 +2056,27 @@ void hotspot_start()
hotspotfd_log();

#ifdef WAN_FAILOVER_SUPPORTED
Copy link
Contributor

@apattu200 apattu200 Dec 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Device.X_COMCAST-COM_GRE.Tunnel.1.TunnelStatus , since it is under WAN_FAILOVER_SUPPORTED, hotspot behavior during down/up will break in CBR which doesn't have this CFLAG

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code change is expected to address the issue - 7176717

With code change ensured the Gerrit verification build passed for all devices - https://gerrit.teamccp.com/#/c/943504/

#ifdef WAN_FAILOVER_SUPPORTED

rbusDataElement_t dataElements[1] = {
{"Device.X_COMCAST-COM_GRE.Tunnel.1.TunnelStatus", RBUS_ELEMENT_TYPE_EVENT | RBUS_ELEMENT_TYPE_PROPERTY, {TunnelStatus_GetStringHandler, TunnelStatus_SetStringHandler, NULL, NULL, NULL, NULL}}
Copy link
Contributor

@apattu200 apattu200 Dec 30, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you please confirm, rbus is not polling for ValueChange when someone subscribes for this parameter. since we have explicit publish this may not be needed.
In rbus code, i could see when element type is not property it won't go for autopublish, but want to double confirm

Otherwise we may need to have explicit subscribe handler with autoPublish setting to false

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This code change is expected to address the issue - 4684824

A separate subscribe handler with autoPublish setting to false is implemented here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants