Implement proper consortium data cache handling at ServicePointSynchronizationHandler during install operation

Description

Issue: ServicePointSynchronizationHandler being called during module install operation, which leads to loading consortium data cache before consortia initialization started which leads to failures during consortium logic, find a way not to use consortium data cache during install

BE Notes: where cache init starts during the install

Find logs attached

Environment

None

Potential Workaround

None

Attachments

1

Checklist

hide

Activity

Show:

Stephanie BuckNovember 21, 2024 at 8:00 PM

Thanks, . I’ll set it as a P3. If it becomes more problematic, let me know and we can bump up the priority and try to get it into a CSP.

Ryan TaylorNovember 21, 2024 at 1:49 PM

- I’ve discussed this with the team and I think we can consider lower priority. Maybe a P3? The issue appears to only occur during first ~5 minutes after module deployed which makes it rare in a customer setup. This is more so an issue for our internal testing.

Stephanie BuckNovember 20, 2024 at 1:32 PM

Hi . Can you help me understand the priority of this ticket? Thank you!!

Details

Assignee

Reporter

Labels

Priority

Development Team

Vega

Release

Trillium (R2 2025)

TestRail: Cases

Open TestRail: Cases

TestRail: Runs

Open TestRail: Runs

Created November 19, 2024 at 2:48 PM
Updated March 5, 2025 at 10:14 PM
TestRail: Cases
TestRail: Runs