GitLab integration troubleshooting

Answers to common bugs and edge cases when using the GitLab Ocean integration.

Why does resync fail with a missing include_only_active_groups attribute?

Answer (click to expand)

The event log shows:

Failed to execute resync function, error: 'Selector' object has
no attribute 'include_only_active_groups'

All file-kind mappings fail during resync.

Cause: This error has two common causes:

1. Invalid selector configuration: The mapping references include_only_active_groups but the selector configuration is malformed or contains unsupported fields for the resource kind being synced. This is the most common cause, even on the latest version.
2. Outdated integration version: On versions older than 0.5.3, the include_only_active_groups attribute is not available in the Selector class.

Fix:

1. Verify your selector configuration is valid for each resource kind in your mapping. Ensure that include_only_active_groups is only used in supported selector contexts and that there are no typos or extra fields.
2. Update the integration to the latest version:
   • Port-hosted: Data Sources → your GitLab integration → click Update if available.
   • Self-hosted: pull the latest image.
3. If updating immediately is not possible, remove any reference to include_only_active_groups from your integration configuration and trigger a manual resync.

---

Why are projects not visible after setting up a group access token?

Answer (click to expand)

After creating a GitLab group access token and installing the integration, fewer projects appear than expected or none at all.

Cause: Group access tokens have scope-based visibility. A token created without the read_api scope, or created at the wrong group level, will return an empty or partial project list without error.

Fix:

1. Verify the token has read_api scope (minimum required).
2. Verify the token is created at the top-level group, not a subgroup, if you want to ingest projects across the full group hierarchy.
3. If you only see projects from one subgroup, the token is scoped to that subgroup only.

---

What are common GitLab integration version compatibility issues?

Answer (click to expand)

When upgrading a self-hosted GitLab integration, breaking changes between minor versions can cause silent failures or incomplete syncs. Always check the integration's changelog before upgrading.

Common version-specific issues:

• v0.6.1: Missing ref parameter causes file-kind mapping failures. Upgrade to v0.6.3 or later.
• v0.6.2: include_only_active_groups attribute error (see the entry above).
• v2 sandbox: Integration may fail in sandbox environments due to stricter SSL verification defaults. Set SSL_VERIFY=false in the integration config for non-production environments only.