Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SDL doesn't provide individual VD result code for clusterModeStatus in SubscribeVehicleData/UnsunscribeVehicleData responses from HMI #3460

Closed
dboltovskyi opened this issue Jul 15, 2020 · 7 comments
Assignees
Labels

Comments

@dboltovskyi
Copy link
Contributor

dboltovskyi commented Jul 15, 2020

Bug Report

SDL doesn't provide individual VD result code for clusterModeStatus in SubscribeVehicleData/UnsunscribeVehicleData responses from HMI in case of 2 apps.

Reproduction Steps

Preconditions:

  1. SDL and HMI are started
  2. SubscribeVehicleData RPC and <vd_param> parameter are allowed by policies
  3. App_1 and App_2 are registered
  4. App_1 successfully subscribes to <vd_param>

In case:

  1. App_2 sends valid SubscribeVehicleData(<vd_param>=true) request to SDL
Expected Behavior

SDL does:

  • send SubscribeVehicleData response with (success = true, resultCode = "SUCCESS", <vd_param> = <data received from HMI>) to App_2
  • not transfer this request to HMI
Observed Behavior

SDL does:

  • not send <vd_param> = <data received from HMI>) in response to App_2
OS & Version Information
Test Case, Sample Code, and / or Example App
@dboltovskyi
Copy link
Contributor Author

Please take into account that for SubscribeVehicleData/UnsunscribeVehicleData real VD parameter name is clusterModes instead of clusterModeStatus
This discrepancy was described in issue #1696

@AKalinich-Luxoft AKalinich-Luxoft self-assigned this Aug 11, 2021
@theresalech
Copy link
Contributor

@dboltovskyi can you please advise if Luxoft is planning to submit a PR to resolve this issue? Thank you!

@dboltovskyi
Copy link
Contributor Author

@theresalech Yes, Luxoft team is planning to submit a fix for this issue.

@ShobhitAd
Copy link
Contributor

Closed via #3830

@VjKlepikov
Copy link

VjKlepikov commented Jan 19, 2022

The issue is reproduced on the current develop branch 8f1ccb2 for new scripts PR 2618
Logs: 2022-01-17_08-33-54.236_failed.tar.gz

Please notice Luxoft team is going to prepare a fix.

@jacobkeeler
Copy link
Contributor

jacobkeeler commented Jan 19, 2022

@VjKlepikov It looks like the failure in smartdevicelink/sdl_atf_test_scripts#2618 is slightly different than the described issue, but similar.

In this case, if the app requests clusterModeStatus in SubscribeVehicleData (along with other parameters) when it does not have permissions for clusterModeStatus.
Core should send clusterModes in the response with the DISALLOWED result code, but instead it omits the clusterModes parameter.

@ShobhitAd
Copy link
Contributor

Closed via #3847

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

7 participants