Congregate Migration - Invalid URI Error and Missing Logs
Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.
Problem Statement
We are encountering an issue during the congregate migration for one of our Clients. And would be interested in a verbose log to pin point the failure. The error observed is as follows:
Error: ERROR: URI::InvalidURIError bad URI (is not URI?): [FILTERED]
This issue specifically arises when migrating projects from our on-prem GitLab instance to GitLab Cloud. Despite reviewing the congregate logs, we have not found any relevant details indicating the root cause. The only notable log entry is:
[2025-02-05 08:17:25,206] ERROR in app: Exception on /api/list-status/c2a59140-28b2-450d-b718-f81107737f3b [GET] raise TypeError(f"Object of type {type(o).name} is not JSON serializable") TypeError: Object of type ConfigurationException is not JSON serializable
Additionally, we were unable to locate any related data/logs, including the import_failed_relations.json file, which is typically generated by the congregate process. At this point, we are uncertain about the exact failure point in the migration.
Reach
This issue affects projects to be migrated from an on-prem GitLab instance to GitLab Cloud using the congregate process.
Reach Score: 3.0 (Significant reach, ~25% to ~50%)
Impact
Resolving this issue will:
Enable successful project migrations without errors.
Reduce manual troubleshooting efforts for affected customers.
Effort
Investigation into where, what and why the URIs are being processed in the migration.
Enhancing logging to capture more details on failures or the component where it has failed.