gitlab-ce-ldap-sync Non-critical error after sync

[error] Gitlab failure: "namespace.route" can't be blank, "notification_email" can't be blank, "notification_email" is invalid

Jun 24 '19 13:06 frafra

I guess this is for new users being created? Which version of Gitlab are you running? (I've not tried this tool on 12 yet.)

Jun 24 '19 16:06 Adambean

Yes, it happens after users creation. I am testing it with GitLab 12.

Jun 25 '19 07:06 frafra

I just ran this against our updated Gitlab 12 instances today. A single new user needed to be created, and did so without any problems.

Are you certain there are valid email addresses assigned to your LDAP users, and that this tool is reading them? If it encounters a user with a non-empty but invalidly formatted email address that could cause it, so if it only happens with one user I'd inspect their object attributes to ensure they're valid.

Jun 27 '19 21:06 Adambean

This error occurred to me as well. In my case it was the "ghost" user from gitlab that was causing it. Try adding userNamesToIgnore: ["ghost"]. If it is not that, check the API logs. I think, this tool should ignore the "ghost" user by default, just as it does with the "root" user.

Jul 31 '19 08:07 beharbunjaku

@beharbunjaku's change has been merged in if you'd like to try it out @frafra.

Jul 31 '19 17:07 Adambean