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 saves wrong custom_vehicle_data_mapping_url version in the DB and sends it in the next ignition cycle #3666

Closed
GetmanetsIrina opened this issue Mar 17, 2021 · 5 comments

Comments

@GetmanetsIrina
Copy link

GetmanetsIrina commented Mar 17, 2021

Bug Report

SDL saves the wrong custom_vehicle_data_mapping_url version in DB and sends it via GetPolicyConfigurationData in the next ignition cycle

Preconditions
  1. sdl_preloaded_pt.json file has version="0.0.0" in custom_vehicle_data_mapping_url structure
  2. SDL and HMI are started
Reproduction Steps
  1. Check custom_vehicle_data_mapping_url version in local DB
  2. Perform IGN_OFF - IGN_ON
  3. Go to HMI main settings → "Policies" → "Send GetPolicyConfigurationData request to SDL" → "Check Custom Vehicle Data Mapping Update Flow"
Expected Behavior
  1. DB contains a value in custom_vehicle_data_mapping_url version that is equal to the value from the sdl_preloaded_pt.json file
  2. In the second ignition cycle SDL sends GetPolicyConfigurationData response with actual custom_vehicle_data_mapping_url version (version="0.0.0")
Observed Behavior
  1. SDL saves wrong value(1) for custom_vehicle_data_mapping_url into the DB
  2. In the second ignition cycle SDL sends GetPolicyConfigurationData response with wrong custom_vehicle_data_mapping_url version (version="1")
  3. SDL adds the custom_vehicle_data_mapping_url entry into the DB each time when an update of OEM data is triggered
OS & Version Information
Logs

SDL log and DB.zip

@jordynmackool
Copy link

jordynmackool commented Mar 18, 2021

Hi @GetmanetsIrina, please advise if Luxoft plans to submit a fix for this reported issue or if Livio can begin working on a PR/ investigating this issue.

@GetmanetsIrina
Copy link
Author

GetmanetsIrina commented Mar 22, 2021

@jordynmackool, This is not a regression issue and due to lack of resources Luxoft team will be able to look at it when 7.1 is released.
Though we don't mind and would appreciate if Livio team is able to fix it.

@LitvinenkoIra
Copy link
Contributor

LitvinenkoIra commented Apr 6, 2021

Hi @jordynmackool, please advise if this issue will be included in the 7.1 release?

@jordynmackool
Copy link

Hi @LitvinenkoIra, as this is noted to not be a regression issue, Livio will plan to investigate it following the 7.1 Release.

@jacobkeeler
Copy link
Contributor

Closing with the merge of #3704

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

No branches or pull requests

4 participants