Done
Details
Assignee
Mykola MakhinMykola MakhinReporter
Artem AkimovArtem AkimovLabels
Priority
P2Story Points
2Sprint
NoneDevelopment Team
EurekaFix versions
Release
Ramsons (R2 2024) Service Patch #1RCA Group
Implementation coding issueTestRail: Cases
Open TestRail: CasesTestRail: Runs
Open TestRail: Runs
Details
Details
Assignee
Mykola Makhin
Mykola MakhinReporter
Artem Akimov
Artem AkimovLabels
Priority
Story Points
2
Sprint
None
Development Team
Eureka
Fix versions
Release
Ramsons (R2 2024) Service Patch #1
RCA Group
Implementation coding issue
TestRail: Cases
Open TestRail: Cases
TestRail: Runs
Open TestRail: Runs
Created February 10, 2025 at 1:32 PM
Updated March 10, 2025 at 12:29 PM
Resolved February 21, 2025 at 11:00 AM
Based on request
and documentation
We are trying to perform kong route migration.
2 errors happened during this migration:
error during deletion of module discovery information. Delete rest API call for /modules/<module_id> return 500. That is what was found in mgr-application logs:
However, service and routes were deleted in Kong. IT’s not a blocker for migration, but it consistently breaks automation and doesn’t look valid.
After that, module registration was performed, and a second issue happened during the entitlement process.
Sidecar logs
2 versions of the same service were found. but since we deleted all other services from Kong, there are no such services or routes in Kong.
After investigation with Kuzminov, we find out that module discovery information for mod-dcb contains information not only for the latest versions of mod-inventory but for other versions of mod-inventory as well.
Scope:
in
ModuleBootstrapService
take only the last version of the module with the provided discovery URLAdd tests