Skip to content

RDKB-60325 notify_tunnel_status failure in hotspot#33

Merged
snayak002c merged 26 commits intordkcentral:developfrom
rajkamal-cv:bug/RDKB-60325
Jan 21, 2026
Merged

RDKB-60325 notify_tunnel_status failure in hotspot#33
snayak002c merged 26 commits intordkcentral:developfrom
rajkamal-cv:bug/RDKB-60325

Conversation

@rajkamal-cv
Copy link
Contributor

@rajkamal-cv rajkamal-cv commented Jan 12, 2026

RDKB-60325 : notify_tunnel_status failure in hotspot

Reason for change:

  1. TunnelStatus_EventSubHandler has been added. autoPublish set to false. - https://github.com/rdkcentral/hotspot/pull/5/files#r2653220170
  2. Modify WAN_FAILOVER_SUPPORTED macro to address the review comment - https://github.com/rdkcentral/hotspot/pull/5/files#r2653184868
  3. Ensure rbus is linked even when WAN_FAILOVER_SUPPORTED macro is not defined

Test Procedure: TunnelStatus should get notified successfully
Risks: Low
Priority: P2

This is also a relevant PR - rdkcentral/provisioning-and-management#156

supriya-shree1 and others added 21 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
Reason for change: notify_tunnel_status fails in hotspot
Test Procedure: TunnelStatus should get notified successfully
Risks: Low
Priority: P2
@rajkamal-cv rajkamal-cv requested review from a team as code owners January 12, 2026 09:33
Reason for change: TunnelStatus_EventSubHandler has been added. autoPublish set to false.
Test Procedure: TunnelStatus should get notified successfully
Risks: Low
Priority: P2
Reason for change: Remove WAN_FAILOVER_SUPPORTED macro to address the review comment
Test Procedure: TunnelStatus should get notified successfully
Risks: Low
Priority: P2
Reason for change:
1. Modify WAN_FAILOVER_SUPPORTED macro to address the review comment
2. Ensure rbus is linked even when WAN_FAILOVER_SUPPORTED macro is not defined
Test Procedure: TunnelStatus should get notified successfully
Risks: Low
Priority: P2
@rajkamal-cv
Copy link
Contributor Author

@snayak002c / @apattu200 please review.

This is also a relevant PR - rdkcentral/provisioning-and-management#156

@apattu200
Copy link
Contributor

@rajkamal-cv Please help with below queries

  1. Is this a Bug or a User Story (US)?
  2. If it is a User Story:
    • Have all dependent PRs from other components been listed (if any)?
    • Does the commit message include both the User Story ticket and the Subtask ticket?
    • Will be all changes related to the User Story squashed and merged in a single commit?
    • Has the PR been raised only after completing all changes for the User Story (no partial changes)?
    • Has code development for the User Story been completed?
      • If yes, has the Gerrit topic or list of all dependent PRs across components (including meta-layer changes) been shared?
  3. Is there a validation log available in the Jira ticket for verifying builds with the updated generic-srcrev.inc across all platforms?
    • If yes, have the links to validation comments been shared?

@rajkamal-cv
Copy link
Contributor Author

@rajkamal-cv Please help with below queries

  1. Is this a Bug or a User Story (US)?

RDKB-60325 is a bug

  1. If it is a User Story:

    • Have all dependent PRs from other components been listed (if any)?

    • Does the commit message include both the User Story ticket and the Subtask ticket?

    • Will be all changes related to the User Story squashed and merged in a single commit?

    • Has the PR been raised only after completing all changes for the User Story (no partial changes)?

    • Has code development for the User Story been completed?

      • If yes, has the Gerrit topic or list of all dependent PRs across components (including meta-layer changes) been shared?
  2. Is there a validation log available in the Jira ticket for verifying builds with the updated generic-srcrev.inc across all platforms?

    • If yes, have the links to validation comments been shared?

Gerrit verification build passed - https://gerrit.teamccp.com/#/c/943504/

The logs are updated in Jira - https://ccp.sys.comcast.net/browse/RDKB-60325?focusedId=24414583&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-24414583

@snayak002c snayak002c merged commit 3a59e6c into rdkcentral:develop Jan 21, 2026
3 of 4 checks passed
@github-actions github-actions bot locked and limited conversation to collaborators Jan 21, 2026
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